-
Notifications
You must be signed in to change notification settings - Fork 475
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
WIP: Update enhancement for aws-load-balancer-operator #1099
WIP: Update enhancement for aws-load-balancer-operator #1099
Conversation
/assign @arjunrn |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
Can you also update the implementation history section. In the drawbacks we should mention that services will also be reconciled. Also in the risk mitigation section for target type IP we can say that this won't work in OpenShift and so is not a risk.
The webhook can be registered with a CA bundle which is used to verify the identity | ||
of webhook by the API server. The [service-ca controller](https://docs.openshift.com/container-platform/4.10/security/certificate_types_descriptions/service-ca-certificates.html) | ||
can be used to generate certificates and have them injected into the webhook | ||
configurations. The operator will also watch the secret with the certificates so |
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.
Currently the secret is not watched. Or rather the secret could be updated in the background and the controller would not cause an update in the deployment of the controller pods to reload the secret. The only way around this if the file is reloaded by controller(not sure if this functionality exists upstream) or if we update the deployment so that it causes a pod rollout.
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.
Addressed.
33f1859
to
66a4316
Compare
fix: template changes fix: api-approvers Signed-off-by: thejasn <thn@redhat.com>
66a4316
to
32a6a34
Compare
@thejasn: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Closing in favor of #1107 |
Update enhancement for
aws-load-balancer-operator