Lab 4.3 Step 7

Built my lab in GCP (after wasting a lot of time on virtual box .... i'm stubborn that way!).
I cant seem to get step 7 to work. ie.e view sock shop app. I've tried adding a firewall rule to GCP but no joy.
Does anyone have any tips ?
Thanks
Comments
-
Hi, I have been using GCP as well and did not run into any issues. I agree that Vbox is quite challenging to setup and complete the labs on it.
Did you get a complete listing of the pods in step 6? Did you get any services listed at all on step 7?
The firewall rule I added in GCP was to enable all traffic.
Will try to run thru the lab again, to see if any behavior has changed...
Regards,
-Chris0 -
what is your all rule for ? any-any internally between the nodes which i believe may be required (never used GCP so starting at the basics) ? or all from the internet ? (in which case good luck!) An idiots guide to getting a cluster up an running on GCP is really needed as part of the course, id rather spend my time learning kube than networking !
0 -
sorry forgot to say - output from steps 6 &7 is as it should be ....
0 -
If both outputs are as expected, then you may just have a firewall issue.
The GCP firewall rules documentation is quite easy to follow:
https://cloud.google.com/vpc/docs/using-firewalls
It gives specific instructions on how to create firewall rules from the console and from the command line thru gcloud command.
Also, verify that the firewall on your VM instances is disabled.
I had to perform these steps on both GCP and AWS in order to get the nodes to communicate with each other and to be able to access the cluster from my laptop.0 -
Got it working thanks, would be good if these steps were included in the lab setup. I know its not too hard to figure out but will be slightly different depending on cloud platform or virtual box (routes?) etc. Will paste my notes below, a bit more detail may help others ....
1 -
If building on GCP you will need a couple of firewall rules when testing external conectivity.
The easiest was to do this is to tag all of your cluster nodes with the same tag. E.g. "k8s" Compute Engine > VM instances > VM Node > Network tags.
GCP has a "default-allow-internal" rule which is based on an IP range, this IP range does not match the calico pod network range, hence the cluster will not work as expected.
To fix this create a new rule "internal-all" as below:
internal-all
Network: default
Priority: 65534
Direction: Ingress
Action on match: Allow
Targets
Target tags: k8s
Source filters
Tags: k8s
Protocols and ports: all
Enforcement: EnabledThis will allow unrestricted pod to pod and pod to node traffic. You will also need a firewall rule to allow traffic from the external world.
E.g.letmein
Network: default
Priority: 65534
Direction: Ingress
Action on match: Allow
Targets
Target tags: k8s
Source filters
IP ranges: 0.0.0.0/0
Protocols and ports: tcp:30001 (Check what node port you want to allow)
Enforcement: EnabledThe second rule could be deleted / disabled when not needed for labs.
0 -
-
An informative video, thanks for sharing.
I looked back at my notes and I only found 1 fw rule I created for my Kubernetes related project. I did not create a VPC or any subnets, so I created the rule for the default network at the project level. The custom rule was very simple: Ingress, Apply to all targets, Range 0.0.0.0/0, All protocols, Allow, 1000. Since all instances in the project were Kubernetes nodes, I figured I'd create one rule to apply to all.
Regards,
-Chris0
Categories
- 9.1K All Categories
- 15 LFX Mentorship
- 68 LFX Mentorship: Linux Kernel
- 382 Linux Foundation Boot Camps
- 234 Cloud Engineer Boot Camp
- 76 Advanced Cloud Engineer Boot Camp
- 30 DevOps Engineer Boot Camp
- 9 Cloud Native Developer Boot Camp
- 982 Training Courses
- 15 LFC110 Class Forum
- 16 LFD102 Class Forum
- 106 LFD103 Class Forum
- 6 LFD121 Class Forum
- 56 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 19 LFD254 Class Forum
- 450 LFD259 Class Forum
- 90 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 16 LFS200 Class Forum
- 715 LFS201 Class Forum
- LFS201-JP クラス フォーラム
- 282 LFS211 Class Forum
- 51 LFS216 Class Forum
- 27 LFS241 Class Forum
- 28 LFS242 Class Forum
- 19 LFS243 Class Forum
- 6 LFS244 Class Forum
- 12 LFS250 Class Forum
- LFS250-JP クラス フォーラム
- 113 LFS253 Class Forum
- 814 LFS258 Class Forum
- 8 LFS258-JP クラス フォーラム
- 54 LFS260 Class Forum
- 81 LFS261 Class Forum
- 18 LFS262 Class Forum
- 76 LFS263 Class Forum
- 15 LFS264 Class Forum
- 10 LFS266 Class Forum
- 10 LFS267 Class Forum
- 9 LFS268 Class Forum
- 6 LFS269 Class Forum
- 183 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 191 LFW211 Class Forum
- 114 LFW212 Class Forum
- 880 Hardware
- 207 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 205 Networking
- 98 Printers & Scanners
- 82 Storage
- 730 Linux Distributions
- 85 Debian
- 64 Fedora
- 12 Linux Mint
- 13 Mageia
- 22 openSUSE
- 127 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 349 Ubuntu
- 450 Linux System Administration
- 33 Cloud Computing
- 64 Command Line/Scripting
- Github systems admin projects
- 89 Linux Security
- 76 Network Management
- 105 System Management
- 45 Web Management
- 51 Mobile Computing
- 19 Android
- 19 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 501 Off Topic
- 121 Introductions
- 193 Small Talk
- 19 Study Material
- 756 Programming and Development
- 243 Kernel Development
- 479 Software Development
- 903 Software
- 247 Applications
- 178 Command Line
- 2 Compiling/Installing
- 73 Games
- 314 Installation
- 26 All In Program
- 26 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)