-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Allow Deploying Multiple Ingress Controllers per Cluster #546
Conversation
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.
controller.reportIngressStatus.externalService
name mismatch has to be addressed.
@Dean-Coakley could |
@dlapcenko That change is reasonable. We'll land that change in a separate PR shortly - as it's not related to: #528 |
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.
Please see my suggestions.
Also, could you update the description of the PR so that it reflects that PR changes?
89a457f
to
dee68b9
Compare
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.
Looking good.
dee68b9
to
0dcece7
Compare
Proposed changes
Re: #528
Fixes: #549
All names of resources created by a deployment must be unique.
By default helm chart now prepends release name to all resources it creates to ensure no conflicts occur when deploying 2 or more ingress controllers in the same namespace.
leaderLockName
now set on daemonsetAdd missing docs about defaultTLS secret to values.yaml
Checklist
Before creating a PR, run through this checklist and mark each as complete.