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

enable_secrets_store_csi_driver_provider_aws : Namespace kube-system already exists #1355

Closed
AndiB42 opened this issue Jan 23, 2023 · 2 comments · Fixed by #1538
Closed

enable_secrets_store_csi_driver_provider_aws : Namespace kube-system already exists #1355

AndiB42 opened this issue Jan 23, 2023 · 2 comments · Fixed by #1538
Labels

Comments

@AndiB42
Copy link

AndiB42 commented Jan 23, 2023

Hello together,

we wanted to enable the secret_store_csi_driver_provider_aws and we're following the documentation here: https://aws-ia.github.io/terraform-aws-eks-blueprints/v4.18.1/add-ons/csi-secrets-store-provider-aws/#usage

We've got this issue:
KubesystemAlreadyExists

It seems, that the configuration of the kubernetes_namespace_v1 resource is not configured as the other addon-modules.
We've tested it locally and found a solution, which would be also a proposal for a Pull-Request:

First:
Because of duplicated cluster-roles, we'd to set the variables like so:

enable_secrets_store_csi_driver = false
enable_secrets_store_csi_driver_provider_aws = true

Second:
in the main.tf of the csi-secrets-store-provider-aws module, we've added this part in line 7:

  count = try(var.helm_config.create_namespace, true) && local.namespace != "kube-system" ? 1 : 0

and of course, the new usage needs to be adapted, like this:

 try(kubernetes_namespace_v1.csi_secrets_store_provider_aws[0].metadata[0].name, local.namespace)

After these steps, it works.
Would you also agree to this proposal?
Or were we misleaded through probably outdated documentation, and maybe it's just necessary to update the documentation?

Thanks in advance for your feedback

@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Feb 23, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2023

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant