We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using a Helm chart, namespace for resources would be taken from current context in ~/.kube/config. That is unexpected.
~/.kube/config
new Helm(this, 'karpenter', { chart: 'oci://public.ecr.aws/karpenter/karpenter', values: { serviceAccount: { annotations: { 'eks.amazonaws.com/role-arn': values.controllerRoleArn } }, settings: { clusterName: values.clusterName, interruptionQueue: values.interruptionQueue, }, webhook: { enabled: false }, }, version: values.version, });
Easily worked around by explicitly setting namespace = this.namespace.
namespace = this.namespace
But this is surprising behaviour, which will lead to generating different manifest from the same code on different machines.
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered:
I believe this is how helm template works. It should be easily reproducible by running the equivalent helm template command.
helm template
Sorry, something went wrong.
Maybe. But the very reason to use cdk8s is to forget the nightmare that Helm is.
Not maybe, it is. You're not escaping anything. You're literally calling helm template.
Whatever, doesn't really matter, the ask stands.
No branches or pull requests
Description of the bug:
When using a Helm chart, namespace for resources would be taken from current context in
~/.kube/config
.That is unexpected.
Reproduction Steps:
Easily worked around by explicitly setting
namespace = this.namespace
.But this is surprising behaviour, which will lead to generating different manifest from the same code on different machines.
Error Log:
Environment:
Other:
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: