You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our company, many teams use the same kubernetes cluster and each team has several namespaces all starting with their designated team-prefix; e.g. team1-namespace1, team2-namespace1, team2-namespace2 etc.
Because team may not see each-others secrets, we are using sealedsecrets in strict mode (include the namespace while encrypting)
But because 1 team has many namespaces, this is a lot of work for each team.
Would it be possible to use just part of the namespacename in the seal process?
In this way, a team kan distribute their sealedsecrets across their own namespaces without the need for resealing.
e.g. if we could have that the seal process only takes the first x characters from the namespacename, that would greatly help our teams.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In our company, many teams use the same kubernetes cluster and each team has several namespaces all starting with their designated team-prefix; e.g. team1-namespace1, team2-namespace1, team2-namespace2 etc.
Because team may not see each-others secrets, we are using sealedsecrets in strict mode (include the namespace while encrypting)
But because 1 team has many namespaces, this is a lot of work for each team.
Would it be possible to use just part of the namespacename in the seal process?
In this way, a team kan distribute their sealedsecrets across their own namespaces without the need for resealing.
e.g. if we could have that the seal process only takes the first x characters from the namespacename, that would greatly help our teams.
Beta Was this translation helpful? Give feedback.
All reactions