Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating sealed secret throws an error: "an empty namespace may not be set when a resource name is provided" #1506

Open
TymenAbels opened this issue Apr 9, 2024 · 1 comment
Labels
triage Issues/PRs that need to be reviewed

Comments

@TymenAbels
Copy link

Which component:
sealed-secrets-controller:0:26.2 , 0:26.1, v0.24.4

Describe the bug
When I apply a .yaml file with kind SealedSecrets and content, The Sealed secret in CustomResourceDefinition sealedsecrets.bitnami.com is created, but the Secret is never created with message below:
an empty namespace may not be set when a resource name is provided
Event(v1.ObjectReference{Kind:"SealedSecret", Namespace:"", Name:"test", UID:"943b4000-9de3-4bb5-8207-cb29a03bffd1", APIVersion:"bitnami.com/v1alpha1", ResourceVersion:"559539446", FieldPath:""}): type: 'Warning' reason: 'ErrUpdateFailed' an empty namespace may not be set when a resource name is provided.
We have tried with multiple versions of the sealed-secrets-controller, 0.26.2, 0.26.1 and v0.24.4 but all results into the same error.
Also when defining a namespace: wihtin the metadata does not sovle this issue.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy Sealed Secrets project version 0.26.2 into AWS EKS version 1.26 using namespace sealed-secrets
  2. Verify pod is launched and image is pulled. Service exist, service accounts with roles and rolebindings.
  3. Create Secret with --dry-run on a client using kubectl
  4. Use kubeseal.exe to fetch certificate.
  5. Use kubeseal.exe to create SealedSecret file.
  6. Apply created SealedSecret to the cluster with kubectl apply -f .yaml

Expected behavior
A SealedSecret resource is created within customresourcedefinition sealedsecret.bitnami.com
kubectl get sealedsecrets will also show the sealedsecret object.
The Secret resource is not created.

Version of Kubernetes:
AWS EKS 1.26

  • Output of kubectl version:
an empty namespace may not be set when a resource name is provided
Event(v1.ObjectReference{Kind:"SealedSecret", Namespace:"", Name:"test", UID:"943b4000-9de3-4bb5-8207-cb29a03bffd1", APIVersion:"bitnami.com/v1alpha1", ResourceVersion:"559539446", FieldPath:""}): type: 'Warning' reason: 'ErrUpdateFailed' an empty namespace may not be set when a resource name is provided

Additional context
Add any other context about the problem here.

@TymenAbels TymenAbels added the triage Issues/PRs that need to be reviewed label Apr 9, 2024
@agarcia-oss
Copy link
Member

Hi @TymenAbels Can you share the exact command line flags you used with kubeseal?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Issues/PRs that need to be reviewed
Projects
None yet
Development

No branches or pull requests

2 participants