-
Notifications
You must be signed in to change notification settings - Fork 544
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
jsonnet: fix rollout-operator ports #10273
Conversation
Fix set ports in deployment, service and webhooks for rollout-operator
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.
The issue #10272 didn't mention why you want the service and containers to use the same port for HTTPS. The current configuration works today and so we don't want to change this.
Using the same service and container port is not essential. The main problem is that only port 8001 was declared in the container, and only port 8443/443 was declared in the service. It turns out that the call from webhooks is unreachable. Changing the ports is just a reduction to a unified approach to creating services (returned to the original one). |
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.
Thanks!
What this PR does
Implements correct port specification for rollout-operator in deployment, service, MutatingWebhookConfiguration and ValidatingWebhookConfiguration
Which issue(s) this PR fixes or relates to
Fixes #10272
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.