-
Notifications
You must be signed in to change notification settings - Fork 9k
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
[bitnami/external-dns] unable to disable validation on external-dns #19942
Labels
external-dns
solved
tech-issues
The user has a technical issue about an application
triage
Triage is needed
Comments
Hi! Thank you so much for the suggestion. Would you like to submit a PR with a value for enabling/disabling the validation? |
jwhitcraft
added a commit
to jwhitcraft/charts-1
that referenced
this issue
Oct 10, 2023
There are some uses cases where the chart value validation should not be ran, this provides a way to disable it. fixes bitnami#19942 Signed-off-by: Jon Whitcraft <[email protected]>
jwhitcraft
added a commit
to jwhitcraft/charts-1
that referenced
this issue
Oct 10, 2023
There are some uses cases where the chart value validation should not be ran, this provides a way to disable it. fixes bitnami#19942 Signed-off-by: Jon Whitcraft <[email protected]>
4 tasks
jwhitcraft
added a commit
to jwhitcraft/charts-1
that referenced
this issue
Oct 11, 2023
There are some uses cases where the chart value validation should not be ran, this provides a way to disable it. fixes bitnami#19942 Signed-off-by: Jon Whitcraft <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
external-dns
solved
tech-issues
The user has a technical issue about an application
triage
Triage is needed
Name and Version
bitnami/external-dns:6.23.3
What architecture are you using?
amd64
What steps will reproduce the bug?
Using ArgoCD with the ArgoCD Vault Plugin, i'm unable to bypass the validation of the external-dns chart.
My use case is that we pass in the path to the secret location inside of Hashicorp Vault and then argocd-vault-plugin does a
helm template --values values.yaml | argocd-vault-plugin generate -
to substitute the path out of the yaml files into the correct values.Which then ARGO will apply to the cluster.
https://github.com/argoproj-labs/argocd-vault-plugin
Are you using any custom parameters or values?
What is the expected behavior?
Outputs the yaml with what was passed in, that way the argocd-vault-plugin can substitute out the values correctly.
What do you see instead?
Error: execution error at (external-dns/charts/external-dns/templates/NOTES.txt:11:3):
VALUES VALIDATION:\nexternal-dns: aws.assumeRoleArn
The AWS Role to assume must follow ARN format:
arn:aws:iam::123455567:role/external-dns
Ref: https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html
Please set a valid ARN (--set aws.assumeRoleARN="xxxx")
Use --debug flag to render out invalid YAML
Additional information
It would be nice to have a flag that could be set to disable the validation, so more advance tools like this could be used.
Thanks,
The text was updated successfully, but these errors were encountered: