Exam CKA topic 1 question 17 discussion

k create ing pong -n ing-internal --rule="/hello=hello:5678"

why there is only 17 Qs and not 20?

killer_sh_lab part2: k get svc -A curl -kL <INTERNAL_IP>/hello # CLUSTER-IP of LoadBalancer -k, --insecure -L, --location

killer_sh_lab part: k create ns ing-internal k run nginx -n=ing-internal --image=nginx --port=80 k expose po nginx -n=ing-internal --name=hello --port=5678 --target-port=80 k get ingressclass vi pong.yml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: pong namespace: ing-internal annotations: nginx.ingress.kubernetes.io/rewrite-target: / spec: ingressClassName: nginx rules: - http: paths: - path: /hello pathType: Prefix backend: service: name: hello port: number: 5678 k apply -f pong.yml

I had the same questions But I did curl I didnt get any response, and after I changed port to 80, I got the correct response

Create a ing-internal.yaml file apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: ping namespace: ing-internal annotations: nginx.ingress.kubernetes.io/rewrite-target: / spec: rules: - http: paths: - path: /hi pathType: Prefix backend: service: name: hi port: number: 5678 kubectl create -f ing-internal.yaml

If you search for Ingress in kubernetes.io.docs you'll find almost the exact answer in the kb for the Ingress resource type.

I have seen several commands listed here but it states it is for nginx so you need to add the nginx annotation like so: k create ing pong -n ing-internal --rule="/hello=hello:5678" --annotation="nginx.ingress.kubernetes.io/rewrite-target=/" Also the debate of pathType: I think the pathType should be exact because the path given is /hello and not /hello* If you disagree and feel that pathType should be Prefix then your command would look like this: k create ing pong -n ing-internal --rule="/hello*=hello:5678" --annotation="nginx.ingress.kubernetes.io/rewrite-target=/"

From other forums I can see some people struggled with this question though it seems very simple. The first thing I would check is to search for the existence of a ingress-controller pod and ingress-controller service. The ingress-controller is mandatory for a ingress to work. I wonder what is the catch with this (easy) question?

Do we need Prefix here? it says path /hello not /hello* ? eny ideas?

How to troubleshoot in case kubectl get ing does not show the ADDRESS? Like in this example: NAME CLASS HOSTS ADDRESS PORTS AGE test-ingress external-lb * 203.0.113.123 80 59s How the Ingress IngressClass is added? Is it needed to add IngressClass? The question does not mention IngressClass name. https://kubernetes.io/docs/concepts/services-networking/ingress/#default-ingress-class

kind: Ingress metadata: name: pong namespace: ing-internal annotations: nginx.ingress.kubernetes.io/rewrite-target: / spec: rules: - http: paths: - path: /hello pathType: Prefix backend: service: name: hello port: number: 5678

apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: pong namespace: ing-internal annotations: nginx.ingress.kubernetes.io/rewrite-target: / spec: ingressClassName: nginx rules: - http: paths: - path: /hello pathType: Prefix backend: service: name: test port: number: 5678

is it necessary to create any service here? what type is the hello service?

is it necessary to create any service here? what type is the hello service?

How can be check the availability of service wit another commands.

Can we change the service port 5678.