Lab 11.2 "503 Service Temporarily Unavailable"
Please help I have been stuck in this lab for 3 weeks
What is the problem?
When I run the command curl -H "Host: www.external.com" http://10.104.227.79 I Got a "503 Service Temporarily Unavailable". I Followed the steps in Lab
I did lab11.2 step 1
Ingress information:
Systmem configuration:
Ingress pods details:
Comments
-
I have got the response in the ingress.yaml, you have to create a ingress for each web server:
- ingress-test-nginx
- ingress-test-httpd
and link the ingress service in spec: to each server web-one or web-two.
Greetings
0 -
Hi @memoros77,
The ingress exercise exemplifies the name based virtual hosting method to route traffic to multiple services through an ingress controller (myingress-ingress-nginx) paired with an ingress object (ingress-test):
https://kubernetes.io/docs/concepts/services-networking/ingress/#name-based-virtual-hosting
Regards,
-Chris0 -
@chrispokorni thank you very much for your answer, It helped me a lot to clarify the concepts!!!
0 -
Hi @memoros77 , I am stuck in exactly similar situation like yours. What did you do to go past that problem and solve 503 issue ?
0 -
I tried to create two ingres to match to same service, but it looks like we can not map to same host, www.external.com.
Error from server (BadRequest): error when creating "ingress2.yaml": admission webhook "validate.nginx.ingress.kubernetes.io" denied the request: host "www.external.com" and path "/" is already defined in ingress default/ingress-test
0 -
@yrimal said:
I tried to create two ingres to match to same service, but it looks like we can not map to same host, www.external.com.Error from server (BadRequest): error when creating "ingress2.yaml": admission webhook "validate.nginx.ingress.kubernetes.io" denied the request: host "www.external.com" and path "/" is already defined in ingress default/ingress-test
You should read through the link provided by Chris earlier for the ingress config. How I got this fixed is that I looked with "describe" command to every single component from top to bottom to see where the network stops and then removed everything and started from beginning since I could not figure out how to re-initialize these components.
My web-two looks like this
apiVersion: apps/v1 kind: Deployment metadata: name: web-two labels: system: secondary namespace: default spec: selector: matchLabels: system: secondary replicas: 1 template: metadata: labels: system: secondary spec: containers: - image: httpd:2.4 imagePullPolicy: Always name: httpd ports: - containerPort: 80 protocol: TCP
Which I expose with command "kubectl expose deployment web-two --type=ClusterIP --name=web-two-svc"
and reference that in my ingress.yml:
apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: ingress-test annotations: nginx.ingress.kubernetes.io/service-upstream: "true" namespace: default spec: ingressClassName: nginx rules: - host: www.external.com http: paths: - backend: service: name: web-two-svc port: number: 80 path: / pathType: ImplementationSpecific
Hope that helps.
0 -
Hi @yrimal,
Just as @mikkokok stated, my earlier response aimed to clarify the purpose of the exercise - to manage traffic to two distinct Services through one single ingress controller paired with one single Ingress object defined by one single manifest. The single ingress manifest stores mapping rules for multiple Services, in our case to Services web-one and web-two respectively.
The ingress exercise exemplifies the name based virtual hosting method to route traffic to multiple services through an ingress controller (myingress-ingress-nginx) paired with an ingress object (ingress-test):
https://kubernetes.io/docs/concepts/services-networking/ingress/#name-based-virtual-hostingRegards,
-Chris0 -
The lab is poorly written. At the top we have this directive: "Create two deployments,web-one and web-two, one running httpd, the other nginx. Expose both as ClusterIP services." Then in the ingress yaml it references a service called "secondapp". It should use the name web-two, as that's the default name of the service for the web-two deployment. Then you just need to copy the rules section and in that rule set change the hostname to perhaps www.webone.com and the service name to web-one. And then they should both work.
0
Categories
- All Categories
- 154 LFX Mentorship
- 154 LFX Mentorship: Linux Kernel
- 665 Linux Foundation IT Professional Programs
- 319 Cloud Engineer IT Professional Program
- 141 Advanced Cloud Engineer IT Professional Program
- 54 DevOps Engineer IT Professional Program
- 120 Cloud Native Developer IT Professional Program
- 91 Express Training Courses
- 91 Express Courses - Discussion Forum
- 5.4K Training Courses
- 19 LFC110 Class Forum - Discontinued
- 12 LFC131 Class Forum
- 32 LFD102 Class Forum
- 191 LFD103 Class Forum
- 9 LFD110 Class Forum
- 24 LFD121 Class Forum
- 14 LFD133 Class Forum
- 14 LFD137 Class Forum
- 62 LFD201 Class Forum
- 2 LFD210 Class Forum
- 1 LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 127 LFD232 Class Forum - Discontinued
- LFD233 Class Forum
- LFD237 Class Forum
- 22 LFD254 Class Forum
- 644 LFD259 Class Forum
- 107 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 7 LFD273 Class Forum
- 2 LFS101 Class Forum
- LFS112 Class Forum
- LFS116 Class Forum
- LFS118 Class Forum
- LFS142 Class Forum
- LFS144 Class Forum
- 2 LFS145 Class Forum
- LFS146 Class Forum
- LFS151 Class Forum
- LFS157 Class Forum
- LFS158 Class Forum
- LFS162 Class Forum
- LFS166 Class Forum
- LFS167 Class Forum
- LFS170 Class Forum
- LFS171 Class Forum
- LFS178 Class Forum
- LFS180 Class Forum
- LFS182 Class Forum
- LFS183 Class Forum
- 28 LFS200 Class Forum
- 735 LFS201 Class Forum - Discontinued
- 1 LFS201-JP クラス フォーラム
- 13 LFS203 Class Forum
- 98 LFS207 Class Forum
- 299 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 36 LFS243 Class Forum
- 12 LFS244 Class Forum
- LFS245 Class Forum
- 42 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 141 LFS253 Class Forum
- LFS254 Class Forum
- LFS255 Class Forum
- 4 LFS256 Class Forum
- LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 9 LFS258-JP クラス フォーラム
- 110 LFS260 Class Forum
- 147 LFS261 Class Forum
- 39 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 20 LFS267 Class Forum
- 18 LFS268 Class Forum
- 26 LFS269 Class Forum
- 198 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- 3 LFS281 Class Forum
- LFW111 Class Forum
- 254 LFW211 Class Forum
- 173 LFW212 Class Forum
- 9 SKF100 Class Forum
- SKF200 Class Forum
- 781 Hardware
- 198 Drivers
- 68 I/O Devices
- 37 Monitors
- 95 Multimedia
- 174 Networking
- 87 Printers & Scanners
- 83 Storage
- 742 Linux Distributions
- 80 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 23 openSUSE
- 143 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 347 Ubuntu
- 460 Linux System Administration
- 40 Cloud Computing
- 69 Command Line/Scripting
- Github systems admin projects
- 89 Linux Security
- 77 Network Management
- 101 System Management
- 46 Web Management
- 51 Mobile Computing
- 17 Android
- 24 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 357 Off Topic
- 109 Introductions
- 169 Small Talk
- 18 Study Material
- 504 Programming and Development
- 283 Kernel Development
- 203 Software Development
- 1.1K Software
- 210 Applications
- 180 Command Line
- 3 Compiling/Installing
- 398 Games
- 308 Installation
- 51 All In Program
- 51 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)