-
Notifications
You must be signed in to change notification settings - Fork 8
Ingress nginx fixes #154
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
Ingress nginx fixes #154
Conversation
This way they're easier to update, and kustomize can see them
912d8ff
to
24fc8d0
Compare
resources: | ||
- configmaps | ||
- pods | ||
- secrets |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this giving ingress-nginx
access to all secrets in all namespaces? O_o
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And I guess the sops
secrets too, trough configmaps
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shrug this is what we already had, I just reorganised it
@daurnimator Could you split the last commit into a follow up PR? I'd be OK merging everything else, but I'd need to look at that last change in more detail. |
24fc8d0
to
5cc43e1
Compare
done. |
@daurnimator The sync attempt failed:
|
So, the workaround for kubernetes-sigs/kustomize#3446 broke, and the bug is still open? 😬 |
Apparently so :( |
No description provided.