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

castai-agent namespace creation template should not be included in castai-agent helm chart #328

Open
karthiktumu opened this issue Oct 6, 2023 · 3 comments

Comments

@karthiktumu
Copy link

We create all our namespaces from a centralized repo to make it easy to apply any kind of labels or annotations we desire to all the workloads running in the namespace.

Before Installing CastAI Agent to our cluster using helm, we created the required namespace (castai-agent) from the above centralized repo. When we try to run a helm install or helm upgrade to deploy castai agent into our cluster, we're running into an issue unable to render manifests for namespace resource as that already exists as shown below

Error: UPGRADE FAILED: rendered manifests contain a resource that already exists. Unable to continue with update: Namespace "castai-agent" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "castai-agent"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "castai-agent"

Please remove the namespace creation manifest from the helm chart for castai-agent so that helm can create the namespace if needed.

I see a similar issue opened in the past but got closed # #135

@fgiannetti
Copy link

fgiannetti commented Oct 19, 2023

Hello!
Same problem here. I am unable to install castAI using Helm getting the same error as @karthiktumu.
Is there any workaround for this?

@geekflyer
Copy link

same issue here. including a namespace resource in the chart itself is highly unusual / uncommon practice.

@geekflyer
Copy link

update:

I found as a workaround one can set createNamespace=false as value for this chart, which disables the namespace creation in the chart. Still would prefer if this resource isn't included to begin with imo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants