How to advertise kubeadm api-server's address?Kubernetes API Server Healthcheck Address with kubeadm
What could be the physiological mechanism for a biological Geiger counter?
Is declining an undergraduate award which causes me discomfort appropriate?
I found a password with hashcat but it doesn't work
Why is it 出差去 and not 去出差?
How would you explain #1 and #2 below using standard quotes?
~te + oku vs plain masu form
Why does a Force divides equally on a Multiple Support/Legs?
Leaving job close to major deadlines
Why was New Asgard established at this place?
What is this word in a sample of blackletter script?
Setting up the trap
Do details of my undergraduate title matter?
reverse a call to mmap()
How "fast" do astronomical events occur?
Are there any individual aliens that have gained superpowers in the Marvel universe?
Is there a polite way to ask about one's ethnicity?
Print the new site header
How can I take pictures like these examples with a yellowish tone and point & shoot film camera look?
Why one uses 了 and the other one doesn’t?
Why are there no file insertion syscalls
Can a character learn spells from someone else's spellbook and then sell it?
Am I legally required to provide a (GPL licensed) source code even after a project is abandoned?
Why do you need to heat the pan before heating the olive oil?
What preparations would Hubble have needed to return in a Shuttle?
How to advertise kubeadm api-server's address?
Kubernetes API Server Healthcheck Address with kubeadm
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I'm trying to set up my first HA cluster with kubeadm. I have haproxy listening on a virtual IP, but that is causing kubeadm init to fail with "port 6443 in use".
Here are the IP addresses, because it's easier than hiding them:
- 192.168.3.37 <-- server IP
- 192.168.3.69 <-- haproxy virtual IP for API
You can see that haproxy is only listening on that virtual IP:
$ sudo lsof -i -P -n | grep 6443
haproxy 12912 haproxy 10u IPv4 99270 0t0 TCP 192.168.3.69:6443 (LISTEN)
Here's my config.yaml for kubeadm:
---
# sudo kubeadm init --experimental-upload-certs --config kubeadm-config.yaml --node-name nuc7i7.home.tedder.me
apiVersion: kubeadm.k8s.io/v1beta1
kind: ClusterConfiguration
kubernetesVersion: stable
controlPlaneEndpoint: "192.168.3.69:6443"
I then call kubeadm as follows:
sudo kubeadm init --experimental-upload-certs --config kubeadm-config.yaml --node-name myhost37
Here, verbatim, is what kubeadm init returns:
[init] Using Kubernetes version: v1.14.2
[preflight] Running pre-flight checks
[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR Port-6443]: Port 6443 is in use
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
If I try to pass --apiserver-advertise-address to kubeadm, it fails:
--apiserver-advertise-address "192.168.3.37"
can not mix '--config' with arguments [apiserver-advertise-address]
I'm not sure why kubeadm is ignoring that bind-address. I'm sure it is ignoring it, I just don't know what to do about it.
kubernetes discovery kubeadm
edited Jun 2 at 11:47
Dave M
4,38992428
asked Jun 2 at 3:47
tedder42tedder42
5441517
add a comment |
I'm trying to set up my first HA cluster with kubeadm. I have haproxy listening on a virtual IP, but that is causing kubeadm init to fail with "port 6443 in use".
Here are the IP addresses, because it's easier than hiding them:
- 192.168.3.37 <-- server IP
- 192.168.3.69 <-- haproxy virtual IP for API
You can see that haproxy is only listening on that virtual IP:
$ sudo lsof -i -P -n | grep 6443
haproxy 12912 haproxy 10u IPv4 99270 0t0 TCP 192.168.3.69:6443 (LISTEN)
Here's my config.yaml for kubeadm:
---
# sudo kubeadm init --experimental-upload-certs --config kubeadm-config.yaml --node-name nuc7i7.home.tedder.me
apiVersion: kubeadm.k8s.io/v1beta1
kind: ClusterConfiguration
kubernetesVersion: stable
controlPlaneEndpoint: "192.168.3.69:6443"
I then call kubeadm as follows:
sudo kubeadm init --experimental-upload-certs --config kubeadm-config.yaml --node-name myhost37
Here, verbatim, is what kubeadm init returns:
[init] Using Kubernetes version: v1.14.2
[preflight] Running pre-flight checks
[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR Port-6443]: Port 6443 is in use
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
If I try to pass --apiserver-advertise-address to kubeadm, it fails:
--apiserver-advertise-address "192.168.3.37"
can not mix '--config' with arguments [apiserver-advertise-address]
I'm not sure why kubeadm is ignoring that bind-address. I'm sure it is ignoring it, I just don't know what to do about it.
kubernetes discovery kubeadm
edited Jun 2 at 11:47
Dave M
4,38992428
asked Jun 2 at 3:47
tedder42tedder42
5441517
I guess the error message you get is quite self-explaining, you cannot specify in two places at the same time '--apiserver-advertise-address' during master node initialization (use either config file kubeadm-config.yaml or command line argument to kubeadm).
– Nepomucen
Jun 7 at 13:20
add a comment |
I'm trying to set up my first HA cluster with kubeadm. I have haproxy listening on a virtual IP, but that is causing kubeadm init to fail with "port 6443 in use".
Here are the IP addresses, because it's easier than hiding them:
- 192.168.3.37 <-- server IP
- 192.168.3.69 <-- haproxy virtual IP for API
You can see that haproxy is only listening on that virtual IP:
$ sudo lsof -i -P -n | grep 6443
haproxy 12912 haproxy 10u IPv4 99270 0t0 TCP 192.168.3.69:6443 (LISTEN)
Here's my config.yaml for kubeadm:
---
# sudo kubeadm init --experimental-upload-certs --config kubeadm-config.yaml --node-name nuc7i7.home.tedder.me
apiVersion: kubeadm.k8s.io/v1beta1
kind: ClusterConfiguration
kubernetesVersion: stable
controlPlaneEndpoint: "192.168.3.69:6443"
I then call kubeadm as follows:
sudo kubeadm init --experimental-upload-certs --config kubeadm-config.yaml --node-name myhost37
Here, verbatim, is what kubeadm init returns:
[init] Using Kubernetes version: v1.14.2
[preflight] Running pre-flight checks
[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR Port-6443]: Port 6443 is in use
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
If I try to pass --apiserver-advertise-address to kubeadm, it fails:
--apiserver-advertise-address "192.168.3.37"
can not mix '--config' with arguments [apiserver-advertise-address]
I'm not sure why kubeadm is ignoring that bind-address. I'm sure it is ignoring it, I just don't know what to do about it.
kubernetes discovery kubeadm
edited Jun 2 at 11:47
Dave M
4,38992428
asked Jun 2 at 3:47
tedder42tedder42
5441517
I'm trying to set up my first HA cluster with kubeadm. I have haproxy listening on a virtual IP, but that is causing kubeadm init to fail with "port 6443 in use".
Here are the IP addresses, because it's easier than hiding them:
- 192.168.3.37 <-- server IP
- 192.168.3.69 <-- haproxy virtual IP for API
You can see that haproxy is only listening on that virtual IP:
$ sudo lsof -i -P -n | grep 6443
haproxy 12912 haproxy 10u IPv4 99270 0t0 TCP 192.168.3.69:6443 (LISTEN)
Here's my config.yaml for kubeadm:
---
# sudo kubeadm init --experimental-upload-certs --config kubeadm-config.yaml --node-name nuc7i7.home.tedder.me
apiVersion: kubeadm.k8s.io/v1beta1
kind: ClusterConfiguration
kubernetesVersion: stable
controlPlaneEndpoint: "192.168.3.69:6443"
I then call kubeadm as follows:
sudo kubeadm init --experimental-upload-certs --config kubeadm-config.yaml --node-name myhost37
Here, verbatim, is what kubeadm init returns:
[init] Using Kubernetes version: v1.14.2
[preflight] Running pre-flight checks
[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR Port-6443]: Port 6443 is in use
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
If I try to pass --apiserver-advertise-address to kubeadm, it fails:
--apiserver-advertise-address "192.168.3.37"
can not mix '--config' with arguments [apiserver-advertise-address]
I'm not sure why kubeadm is ignoring that bind-address. I'm sure it is ignoring it, I just don't know what to do about it.
kubernetes discovery kubeadm
kubernetes discovery kubeadm
edited Jun 2 at 11:47
Dave M
4,38992428
asked Jun 2 at 3:47
tedder42tedder42
5441517
edited Jun 2 at 11:47
Dave M
4,38992428
asked Jun 2 at 3:47
tedder42tedder42
5441517
edited Jun 2 at 11:47
Dave M
4,38992428
edited Jun 2 at 11:47
Dave M
4,38992428
edited Jun 2 at 11:47
Dave M
4,38992428
4,38992428
asked Jun 2 at 3:47
tedder42tedder42
5441517
asked Jun 2 at 3:47
tedder42tedder42
5441517
asked Jun 2 at 3:47
tedder42tedder42
5441517
5441517
I guess the error message you get is quite self-explaining, you cannot specify in two places at the same time '--apiserver-advertise-address' during master node initialization (use either config file kubeadm-config.yaml or command line argument to kubeadm).
– Nepomucen
Jun 7 at 13:20
add a comment |
I guess the error message you get is quite self-explaining, you cannot specify in two places at the same time '--apiserver-advertise-address' during master node initialization (use either config file kubeadm-config.yaml or command line argument to kubeadm).
– Nepomucen
Jun 7 at 13:20
I guess the error message you get is quite self-explaining, you cannot specify in two places at the same time '--apiserver-advertise-address' during master node initialization (use either config file kubeadm-config.yaml or command line argument to kubeadm).
– Nepomucen
Jun 7 at 13:20
I guess the error message you get is quite self-explaining, you cannot specify in two places at the same time '--apiserver-advertise-address' during master node initialization (use either config file kubeadm-config.yaml or command line argument to kubeadm).
– Nepomucen
Jun 7 at 13:20
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f969816%2fhow-to-advertise-kubeadm-api-servers-address%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f969816%2fhow-to-advertise-kubeadm-api-servers-address%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I guess the error message you get is quite self-explaining, you cannot specify in two places at the same time '--apiserver-advertise-address' during master node initialization (use either config file kubeadm-config.yaml or command line argument to kubeadm).
– Nepomucen
Jun 7 at 13:20