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
Using the example here https://argo-cd.readthedocs.io/en/stable/user-guide/helm/#declarative results in a lot of kubeseal cli issues.
What change you think needs making.
Very confusing since its a ready made example snippet.
Change namespace to kube-system
apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: sealed-secrets namespace: argocd spec: project: default source: chart: sealed-secrets repoURL: https://bitnami-labs.github.io/sealed-secrets targetRevision: 1.16.1 # could also change the version to 2.1.0 helm: releaseName: sealed-secrets destination: server: https://kubernetes.default.svc namespace: kube-system
The text was updated successfully, but these errors were encountered:
@ishitasequeira no update here? Snipped still has a custom namespace: kubeseal.
namespace: kubeseal
Sorry, something went wrong.
Not sure if this is still an issue in newest version (we are still using kube-system) so cant test it but if it is fixed it can be closed.
No branches or pull requests
Summary
Using the example here
https://argo-cd.readthedocs.io/en/stable/user-guide/helm/#declarative
results in a lot of kubeseal cli issues.
What change you think needs making.
Motivation
Very confusing since its a ready made example snippet.
Proposal
Change namespace to kube-system
The text was updated successfully, but these errors were encountered: