Use DNS names vs IP for etcd and kube-apiserver? (re: Lab 3.1)

It seems that when you install k8, etcd and kube-apiserver is configured to use the IP of the k8 master. That is an issue to me as I do tear down my environment and start it back up.
Is there a way to tell to use the hostname/dns name of the master rather than the IP?
Comments
-
Hello,
The x509 certificates will only work with the server name passed to kubeadm init. I would suggest starting over and following the entire directions, where you configure the k8smaster alias and use it. This will become essential when you try to get HA to work.
Regards,
0 -
Hi @rilindo,
In some environments the VMs get to keep their private IP addresses between restarts. In others, you may assign static IP addresses to your VMs.
Are you using a cloud or local infrastructure?
Regards,
-Chris0 -
@serewicz This is how I configure things, per instructions:
root@k8smaster:~# cat kubeadm-config.yaml apiVersion: kubeadm.k8s.io/v1beta2 kind: ClusterConfiguration kubernetesVersion: stable controlPlaneEndpoint: "k8smaster:6443" networking: podSubnet: 192.168.0.0/16 root@k8smaster:~# cat /etc/hosts # Your system has configured 'manage_etc_hosts' as True. # As a result, if you wish for changes to this file to persist # then you will need to either # a.) make changes to the master file in /etc/cloud/templates/hosts.debian.tmpl # b.) change or remove the value of 'manage_etc_hosts' in # /etc/cloud/cloud.cfg or cloud-config from user-data # 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts 10.70.60.49 k8smaster k8smaster /usr/bin/kubeadm init --config=/root/kubeadm-config.yaml --upload-certs | tee /root/kubeadm-init.out
Essentially, what it says in the lab
@chrispokorni I am using scaleway as a cloud provider and they don't allow you to assign IP addresses manually.
I am not against having to use Tier 1 provider like AWS (since they provide that capability), but I am hoping that it doesn't come to that.
0 -
Hello,
Could you indicate where you see it using the IP instead of the k8smaster alias?
Could you show grep server .kube/config output please.
Regards,
0 -
Hello,
Also what operating system and cloud provider or host are you using?I note this in your output:
Your system has configured 'manage_etc_hosts' as True. # As a result, if you wish for changes to this file to persist # then you will need to either # a.) make changes to the master file in /etc/cloud/templates/hosts.debian.tmpl # b.) change or remove the value of 'manage_etc_hosts' in # /etc/cloud/cloud.cfg or cloud-config from user-data
Regards,
0 -
@serewicz Here is my kube config:
gstudent@k8smaster:~$ grep server .kube/config server: https://k8smaster:6443 student@k8smaster:~$
The IPs in question are located here:
root@k8smaster:~# find /etc/ -type f -exec grep -l 10.68.68.191 {} \; /etc/hosts /etc/kubernetes/manifests/etcd.yaml /etc/kubernetes/manifests/kube-apiserver.yaml
Also:
Also what operating system and cloud provider or host are you using?
I am using Ubuntu Bionic on Scaleway.
root@k8smaster:~# uname -a Linux k8smaster 4.15.0-115-generic #116-Ubuntu SMP Wed Aug 26 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@k8smaster:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS"
And
I note this in your output:
Scaleway uses cloud-init, which does some configuration inject at start. I had it off and turn it back on (since I am using ansible to reconfigure the the host file):
- /usr/bin/ansible 127.0.0.1 -m lineinfile -a 'dest=/etc/hosts regexp=".*k8smaster.*" line="{{ ipaddress }} k8smaster k8smaster" state=present' -e ipaddress=$(ifdata -pa ens2)
0 -
Alright, I bit the bullet and switch over to AWS, which allowed me to set a static private IP. That said. . . . maybe I should try a different approach, since it seems that AWS behavior on static private IPs seems to be inconsistent.
If the the master somehow start up with a different IP, is it possible to re-run kubeadm init to rebuild the configuration with a different IP?
0 -
I have been using Google Cloud GCE VM instances for my Kubernetes clusters for a few years now, and have not encountered any issues when re-starting my clusters. That is probably because GCE keeps the private IPs static in my custom VPC network.
There is a
kubeadm reset
command you could run on master and worker nodes if this is something you desire, but the command itself is not perfect, as it leaves behind configuration options which need to be cleaned up manually post-reset, otherwise you will not be able to seamlessly re-join your nodes in a cluster. Additional cleanup steps are described here.However, unless this process is scripted/automated, I find this to be a counterproductive approach.
Regards,
-Chris0 -
@chrispokorni Sounds like at some point I may need to start using Google Cloud GCE to get some sort of first class support for Kubenetes. FWIW, after some refactoring my lab (enlarging my CIDR to avoid IP address complexity), the AWS setup seems to be working out well, so I will continue on that as of this time.
Thanks to y'all for your help!
0
Categories
- All Categories
- 50 LFX Mentorship
- 103 LFX Mentorship: Linux Kernel
- 575 Linux Foundation IT Professional Programs
- 304 Cloud Engineer IT Professional Program
- 125 Advanced Cloud Engineer IT Professional Program
- 53 DevOps Engineer IT Professional Program
- 60 Cloud Native Developer IT Professional Program
- 5 Express Training Courses
- 5 Express Courses - Discussion Forum
- 2K Training Courses
- 19 LFC110 Class Forum
- 7 LFC131 Class Forum
- 27 LFD102 Class Forum
- 156 LFD103 Class Forum
- 20 LFD121 Class Forum
- 1 LFD137 Class Forum
- 61 LFD201 Class Forum
- 1 LFD210 Class Forum
- LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 611 LFD259 Class Forum
- 105 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFD273 Class Forum
- 2 LFS145 Class Forum
- 24 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 10 LFS203 Class Forum
- 75 LFS207 Class Forum
- 300 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 11 LFS244 Class Forum
- 34 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 140 LFS253 Class Forum
- LFS254 Class Forum
- 1.1K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 93 LFS260 Class Forum
- 132 LFS261 Class Forum
- 33 LFS262 Class Forum
- 80 LFS263 Class Forum
- 15 LFS264 Class Forum
- 11 LFS266 Class Forum
- 18 LFS267 Class Forum
- 17 LFS268 Class Forum
- 23 LFS269 Class Forum
- 203 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- LFS281 Class Forum
- 233 LFW211 Class Forum
- 172 LFW212 Class Forum
- 7 SKF100 Class Forum
- SKF200 Class Forum
- 902 Hardware
- 219 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 209 Networking
- 101 Printers & Scanners
- 85 Storage
- 763 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 142 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 357 Ubuntu
- 479 Linux System Administration
- 41 Cloud Computing
- 70 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 78 Network Management
- 108 System Management
- 49 Web Management
- 68 Mobile Computing
- 23 Android
- 30 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 537 Off Topic
- 131 Introductions
- 217 Small Talk
- 21 Study Material
- 826 Programming and Development
- 278 Kernel Development
- 514 Software Development
- 928 Software
- 260 Applications
- 184 Command Line
- 3 Compiling/Installing
- 76 Games
- 316 Installation
- 62 All In Program
- 62 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)