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.

Sign up for GitHub

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

Jump to bottom

Worker node receives incorrect port for kube-apiserver on Master node for kubeadm join #64

Closed
scruplelesswizard opened this issue Oct 18, 2018 · 8 comments
Closed

Worker node receives incorrect port for kube-apiserver on Master node for kubeadm join #64

scruplelesswizard opened this issue Oct 18, 2018 · 8 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@scruplelesswizard
Copy link
Contributor

The kubeadm join on worker nodes is provided the wrong port (443) for the kube-apiserver on the master node, i.e.

kubeadm join --token <redacted> 10.10.10.1:443 --ignore-preflight-errors=all --discovery-token-unsafe-skip-ca-verification
[preflight] running pre-flight checks
[discovery] Trying to connect to API Server "10.10.10.1:443"
[discovery] Created cluster-info discovery client, requesting info from "https://10.10.10.1:443"

The configured port for the kube-apiserver is 6443, resulting in worker nodes being unable to join the cluster.
@scruplelesswizard
Copy link
Contributor Author

It appears that the UpdateClusterObjectEndpoint func uses a const to set the port, disregarding any kube-apiserver configuration

@Lion-Wei
Copy link

Hi, any update about this issue?

@scruplelesswizard
Copy link
Contributor Author

Not yet, I haven't had free cycles to continue investigating this

@flaper87
Copy link
Contributor

I've created an issue on cluster-api: kubernetes-sigs/cluster-api#559 We can workaround this issue if we just use 443 for now. Trying to figure out a good way to solve this

flaper87 added a commit to flaper87/cluster-api-provider-openstack that referenced this issue Oct 25, 2018
@flaper87
Use 443 until cluster-api is fixed
d43f440 
Use 443 as the apiserver port until cluster-api allows us to set a
different port instead of hard-coding it:

kubernetes-sigs#64
@flaper87 flaper87 mentioned this issue Oct 25, 2018
Merged
k8s-ci-robot pushed a commit that referenced this issue Oct 25, 2018
@flaper87 @k8s-ci-robot
Use 443 until cluster-api is fixed (#77)
e26c079 
Use 443 as the apiserver port until cluster-api allows us to set a
different port instead of hard-coding it:

#64
flaper87 added a commit to openshift/cluster-api-provider-openstack that referenced this issue Nov 29, 2018
@flaper87
Use 443 until cluster-api is fixed (#77)
dbca404 
Use 443 as the apiserver port until cluster-api allows us to set a
different port instead of hard-coding it:

kubernetes-sigs#64
@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-testing, kubernetes/test-infra and/or fejta.
/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 Apr 26, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 26, 2019
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

iamemilio pushed a commit to iamemilio/cluster-api-provider-openstack that referenced this issue Sep 25, 2019
@openshift-merge-robot
Merge pull request kubernetes-sigs#64 from Fedosin/invalid_label
8bec080 
Bug 1747245: return an error if the cluster name label is incorrect
pierreprinetti pushed a commit to shiftstack/cluster-api-provider-openstack that referenced this issue Apr 22, 2024
@flaper87 @pierreprinetti
Use 443 until cluster-api is fixed (openshift#77)
fc9021f 
Use 443 as the apiserver port until cluster-api allows us to set a
different port instead of hard-coding it:

kubernetes-sigs#64
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@flaper87 @scruplelesswizard @k8s-ci-robot @Lion-Wei @fejta-bot