Lab 7.3 review : clarification
- Create a new pod called
webone
, running the
nginx
service. Expose port 80. - Create a new service named
webone-svc
. The service should be accessible from outside the cluster. - Update both the pod and the service with selectors so that traffic for to the service IP shows the web server content.
at step 3. I don't understand what it means by web server content.
here what I did (without giving the complete answers...)
1. create a pod named : webone : nginx, port 80
2 - expose webone port 80, loadbalancer
3 - my loadbalancer ip is : 192.168.50.200, so I did curl http://192.168.50.200 and I got the results of nginx index page
I didn't update anything in step 3.. so I think that I didn't do it correctly ?
Comments
-
- Change the type of the service such that it is only accessible from within the cluster. Test that exterior access no longer
works, but access from within the node works.
I change the service to : ClusterIP. I think that works.
Deploy pod, webtwo, .. OK done
Install and configure an ingress controller such that requests for webone.com see the nginx default page, and requests
for webtwo.org see the wlniao/website default page.
I'm not able to get the http output for this step.
I created a ingress yaml like this
apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: ingress-review spec: rules: - host: webone.com http: paths: - pathType: Prefix path: / backend: service: name: webone-svc port: number: 80 - host: webtwo.org http: paths: - pathType: Prefix path: / backend: service: name: webtwo-svc port: number: 80
here my ingress
kubectl get ingress Warning: extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress NAME CLASS HOSTS ADDRESS PORTS AGE ingress-test <none> www.example.com,thirdpage.org 192.168.50.202 80 24h ingress-wildcard-host <none> webone.com,webtwo.org 192.168.50.202 80 10m curl -H "Host: webone.com" http://196.168.50.202/ (it stall here)
1 - Change the type of the service such that it is only accessible from within the cluster. Test that exterior access no longer
-
Hi @SebastienDionne,
There are multiple ways to create a service to expose an application. The
expose
method ensures that the service object inherits from the application it exposes all the correct binding parameters, such as thelabel
andselector
. There is another method tocreate service
where a generic/independent service is created, not bound to any application. That service may need to be edited for the logical bind to take place.For your ingress, do you have all permissions in place?
Do you have a controller installed (traefik, nginx, ...)?
Does your ingress object have the expected annotations in place, specific to the controller you are using?
Does the name of your service match the backend.service.name property of the ingress rule?
Can you access services over the x.y.z.202 IP address?Regards,
-Chris0 -
thanks, so I was OK for the service. It's true that I could have use different methods. I just wanted to be sure that what I did was OK. The problem is that we don't have the answer for the review exercises.
For my error I deleted all the services, ingress and deleted my metallb pods.. and used ingress : extensions/v1beta1 instead of v1. everything work now. I'll have to try with the example on Kubernetes docs, they are using v1
0 -
Hi,
I'm also confused about the wording of the tasks.
If I follow the tasks exactly as indicated, should I end up with two services (the one created through
expose
in Task 1 and the one created as part of Task 2 - be it throughcreate
,yaml
orexpose
again)?For instance:
- Create a new pod called webone, running the nginx service. Expose port 80.
What is the meaning of "expose" here? The pod can already be reached internally through port 80 even if there's no service created (since
nginx
listens to port 80 by default).Clarification is appreciated. Thanks!
0 -
Hi @gerardocl,
Exposing an application through a Service object ensures service discovery via the cluster DNS for the exposed application.
It is true that a Pod can be accessed directly via its IP address, but any app that needs to access the Pod would have to somehow retrieve the IP of the desired Pod. This is not a feature of the cluster, so that would have to be implemented separately, and it may introduce some overhead.
Regards,
-Chris0 -
It is works after I add the annotation in ingress.yaml:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress-review
annotations:
# nginx.ingress.kubernetes.io/service-upstream: "true"
nginx.ingress.kubernetes.io/rewrite-target: /$1
spec:
ingressClassName: nginx
rules:
- host: webone.com
http:
paths:
- pathType: Prefix
path: /
pathType: ImplementationSpecific
backend:
service:
name: webone-svc
port:
number: 80
- host: webtwo.org
http:
paths:
- pathType: Prefix
path: /
pathType: ImplementationSpecific
backend:
service:
name: webtwo-svc
port:
number: 800
Categories
- All Categories
- 60 LFX Mentorship
- 113 LFX Mentorship: Linux Kernel
- 618 Linux Foundation IT Professional Programs
- 321 Cloud Engineer IT Professional Program
- 142 Advanced Cloud Engineer IT Professional Program
- 55 DevOps Engineer IT Professional Program
- 68 Cloud Native Developer IT Professional Program
- 6 Express Training Courses
- 6 Express Courses - Discussion Forum
- 2.3K Training Courses
- 19 LFC110 Class Forum - Discontinued
- 9 LFC131 Class Forum
- 31 LFD102 Class Forum
- 175 LFD103 Class Forum
- 22 LFD121 Class Forum
- 2 LFD137 Class Forum
- 61 LFD201 Class Forum
- 2 LFD210 Class Forum
- 1 LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 653 LFD259 Class Forum
- 108 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 4 LFD273 Class Forum
- 2 LFS145 Class Forum
- 28 LFS200 Class Forum
- 740 LFS201 Class Forum - Discontinued
- 1 LFS201-JP クラス フォーラム
- 12 LFS203 Class Forum
- 92 LFS207 Class Forum
- 301 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 12 LFS244 Class Forum
- 41 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 142 LFS253 Class Forum
- LFS254 Class Forum
- LFS255 Class Forum
- LFS256 Class Forum
- LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 106 LFS260 Class Forum
- 145 LFS261 Class Forum
- 39 LFS262 Class Forum
- 83 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
- 204 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- 3 LFS281 Class Forum
- 249 LFW211 Class Forum
- 177 LFW212 Class Forum
- 9 SKF100 Class Forum
- SKF200 Class Forum
- 907 Hardware
- 220 Drivers
- 74 I/O Devices
- 44 Monitors
- 116 Multimedia
- 210 Networking
- 102 Printers & Scanners
- 86 Storage
- 764 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 143 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 357 Ubuntu
- 482 Linux System Administration
- 40 Cloud Computing
- 70 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 80 Network Management
- 108 System Management
- 51 Web Management
- 72 Mobile Computing
- 25 Android
- 32 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 545 Off Topic
- 132 Introductions
- 223 Small Talk
- 22 Study Material
- 831 Programming and Development
- 282 Kernel Development
- 515 Software Development
- 974 Software
- 260 Applications
- 185 Command Line
- 3 Compiling/Installing
- 119 Games
- 318 Installation
- 65 All In Program
- 65 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)