template.metadata.name ignored in sealed secret about sealed-secrets HOT 4 OPEN

NOTE: the kubernetes version is a bit old (I have no control over that). However, the issue should also occur on newer clusters since it is the sealed secret operator that finally decides what the name of the generated secret should be.

from sealed-secrets.

Just encountered this myself, guessing this is what's causing it:

Is there a reason the name/namespace need to match the SealedSecret metadata?

from sealed-secrets.

From the docs:

Note the SealedSecret and Secret must have the same namespace and name. This is a feature to prevent other users on the same cluster from re-using your sealed secrets. See the Scopes section for more info.

from sealed-secrets.

shouldn't the metadata.name configuration be removed then from the template? Having this parameter there suggests that it can be independently configured of the name of the sealedsecret. Right now it silently ignores the name.

Alternatively, users could also be warned in the output of kubectl describe and in the status field of the secret. I realize the change would be downwards incompatible.

from sealed-secrets.