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

Allow workload cluster API LB frontend port to be configured distinctively from apiserver listen port #1240

Closed
tuommaki opened this issue Mar 16, 2021 · 3 comments
Labels
kind/proposal Issues or PRs related to proposals. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@tuommaki
Copy link

Goals

  1. Allow distinct configuration of API LB frontend port from apiserver listen port.
  2. Maintain current behavior to default with apiserver listen port when control plane endpoint port has not been defined.

User Story

As an operator I would like to configure different port to public facing API LB frontend port than what workload cluster's k8s apiserver uses as listen port.

Detailed Description

As an operator I want API LB frontend port to listen in default HTTPS port (443) while workload cluster's control plane nodes have kubernetes apiserver bound in non-privileged default port 6443.

Contract changes [optional]

If Cluster.Spec.ControlPlaneEndpoint.Port has been defined, it's used for API LB frontend port configuration. If it is not defined, API LB frontend port defaults to workload cluster kubernetes apiserver listen port as it is used now.

Data model changes [optional]

No changes to data model is needed for this feature.

/kind proposal

@k8s-ci-robot k8s-ci-robot added the kind/proposal Issues or PRs related to proposals. label Mar 16, 2021
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 14, 2021
@tuommaki
Copy link
Author

tuommaki commented Jul 5, 2021

We haven't had a need for this now and since there wasn't any other traction on this, I'll close this ticket.

@tuommaki tuommaki closed this as completed Jul 5, 2021
@dmeytin
Copy link

dmeytin commented Jul 25, 2021

Hey Tuomas,
If I remember correctly, reusing the same port has caused the workload that is running on master nodes and performs communication with k8s api servers to fail when the same node where the instance is running was accessed.
Was this use-case validated?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/proposal Issues or PRs related to proposals. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants