Skip to content
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

Merged
merged 6 commits into from Aug 16, 2022

Conversation

embik
Copy link
Member

@embik embik commented Aug 15, 2022

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 and ingress-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:

Add EnableIngressHostname and IngressHostnameSuffix options for Openstack (enables workaround in Openstack CCM for PROXY protocol client IP preservation)

Documentation:

NONE

Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
@kubermatic-bot kubermatic-bot added kind/feature Categorizes issue or PR as related to a new feature. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Aug 15, 2022
@kubermatic-bot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@kubermatic-bot kubermatic-bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Aug 15, 2022
@embik
Copy link
Member Author

embik commented Aug 15, 2022

/test pre-kubermatic-e2e-openstack-ubuntu-1.24

@embik embik marked this pull request as ready for review August 15, 2022 07:32
@kubermatic-bot kubermatic-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Aug 15, 2022
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
@kubermatic-bot kubermatic-bot added sig/api Denotes a PR or issue as being assigned to SIG API. and removed approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 15, 2022
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
@embik
Copy link
Member Author

embik commented Aug 15, 2022

/test pre-kubermatic-e2e-openstack-ubuntu-1.24

@embik
Copy link
Member Author

embik commented Aug 15, 2022

/retest

@embik embik added this to the KKP 2.21 milestone Aug 15, 2022
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Copy link
Member

@xmudrii xmudrii left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Aug 15, 2022
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 763e1ebbd8714b2548a712dcf2b0e54adf88a84a

@embik
Copy link
Member Author

embik commented Aug 15, 2022

/retest

Copy link
Member

@ahmedwaleedmalik ahmedwaleedmalik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve 🦀

@kubermatic-bot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 16, 2022
@kubermatic-bot kubermatic-bot merged commit 4929918 into kubermatic:master Aug 16, 2022
@embik embik deleted the enable-ingress-hostname branch August 16, 2022 06:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/api Denotes a PR or issue as being assigned to SIG API. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Adding enable-ingress-hostname setup as a field or annotation
4 participants