Lab2.2 time out errors when trying to ssh back into the nodes. Noticed firewall rules changed.

In exercise 2.2, after running the bash scripts to install kubernetes on both the master and worker nodes, and connecting them using the kubeadm join statement, I walked away from my computer for a bit. When I returned, and tried to ssh back into the master and worker nodes I'm getting a timeout error. When I checked the firewall rules I noticed the "lfclass" firewall rule I initially created where the "Direction of traffic": "ingress", "action on match": "allow") is missing! There are a bunch of new firewall rules, including one for ingress where "Protocols/Ports"="all" and "Action"="Deny"
What happened? Is this expected? How can I ssh into the nodes as I did previously?
Thanks,
Ryan
Comments
-
Hi Ryan,
The behavior of your environment is unexpected and unique. We have no control over learners' environments, and the installation scripts for both master and second nodes do not interfere in any way with the lab infrastructure. Kubernetes does not manage the underlying infrastructure, it only uses it as it is configured by the user. Any infra misconfiguration will not be "fixed" by Kubernetes.
From my experience, creating a new custom VPC together with a custom all-open/allow-all firewall rule works very well. I was able to spin up hundreds of Kubernetes clusters of various sizes, in that same VPC, and never encountered any such issues.
Regards,
-Chris0 -
Do you have any thoughts on how this could have happened? I was ssh-ed into both the master node (in one terminal session) and the worker node (in another terminal session) when I walked away. And when I returned to my computer I was logged out. When I tried to SSH back in I received the timeout errors in which I then began looking at the firewall rules. In the course video, "Using GCE to Set Up Labs" we only set up one firewall rule which was to allow all ingress from any protocol and port. However, this is what my firewall rules page looks like now:
...I did not create any of these, so I'm assuming that either the installation scripts (k8sMaster.sh, k8sSecond.sh), or the kubeadm join command must have created these?
0 -
Hello,
The scripts would not have been able to do this. These scripts are run inside of the nodes. The nodes would have no access to your GCE console. I've not seen anything like this. Could something have been on the keyboard like a book or something and some sort of strange loop started? A co-workers messing with you?
I would probably clear out all but the one all-open rule mentioned in the video. I can assure you this was not caused by the script, or anything done according to the lab exercises.
Regards,
0 -
I was able to solve the issue. I believe the issue I was facing was due to enforcers that are in place to restrict incoming traffic at the GCP Organization level for the GCP Organization that my project was created under. I recreated a different project under a different GCP Org and used the same keys and it's working.
Thanks,
Ryan0 -
Glad to hear it all works now. That explains the additional firewall rules which may have been created automatically on your behalf.
Regards,
-Chris0
Categories
- All Categories
- 51 LFX Mentorship
- 104 LFX Mentorship: Linux Kernel
- 576 Linux Foundation IT Professional Programs
- 304 Cloud Engineer IT Professional Program
- 125 Advanced Cloud Engineer IT Professional Program
- 53 DevOps Engineer IT Professional Program
- 61 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
- 157 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 クラス フォーラム
- 11 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
- 36 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
- 235 LFW211 Class Forum
- 172 LFW212 Class Forum
- 7 SKF100 Class Forum
- SKF200 Class Forum
- 903 Hardware
- 219 Drivers
- 74 I/O Devices
- 44 Monitors
- 116 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
- 61 All In Program
- 61 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)