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
Add EnableIngressHostname and IngressHostnameSuffix options to Openstack cloud spec #10751
Add EnableIngressHostname and IngressHostnameSuffix options to Openstack cloud spec #10751
Conversation
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Skipping CI for Draft Pull Request. |
/test pre-kubermatic-e2e-openstack-ubuntu-1.24 |
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
/test pre-kubermatic-e2e-openstack-ubuntu-1.24 |
/retest |
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
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.
/lgtm
/approve
LGTM label has been added. Git tree hash: 763e1ebbd8714b2548a712dcf2b0e54adf88a84a
|
/retest |
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.
/approve 🦀
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmedwaleedmalik, embik, xmudrii The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
The Openstack CCM has some workaround for using the PROXY protocol, as using that on a load balancer seems to break when you try to connect to the public IP from another node or pod in the cluster (so in-cluster components cannot talk to the service). The workaround seems to set up a dummy DNS name on the LoadBalancer service. That is configured by
enable-ingress-hostname
andingress-hostname-suffix
. See upstream docs for details on these options.Upstream might remove this in the future once Kubernetes fixes the root issue via KEP-1860, so we should be ready to deprecate and remove this option in the future.
Which issue(s) this PR fixes:
Fixes #10706
What type of PR is this?
/kind feature
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: