Hello, i believe there are some issues / not clear tasks, etc. Please share your thoughts:
Task 1: There is a pod called pink-pod-cka16-trb created in the default namespace in cluster4. This app runs on port tcp/5000 and it is exposed to end-users using an ingress resource called pink-ing-cka16-trb in such a way that it is supposed to be accessible using the command: curl http://kodekloud-pink.app on cluster4-controlplane host.
- curl kodekloud-pink.app # it gives 404, not 503 like in solution
- There is no ingress resource
- Also, after scaling coredns - it still doesn’t work, there is a 404. So basically - suggested solution doesn’t work.
Please double check that task.
Task 2: On cluster3, there is a web application pod running inside the default namespace. This pod which is part of a deployment called webapp-color-wl10 and makes use of an environment variable that can change constantly. Add this environment variable to a configmap and configure the pod in the deployment to make use of this config map.
Suggested solution was:
envFrom:
- configMapRef:
…
While i did it like this and it worked, i believe you should allow it as well:
- env:
- name: APP_COLOR
valueFrom:
configMapKeyRef:
…
not so important Task3: Create a service account called pink-sa-cka24-arch. Further create a cluster role called pink-role-cka24-arch with full permissions on all resources in the core api group under default namespace in cluster1.
- It is a bit misleading “a cluster role bla bla under namespace”, as you can’t limit cluster role to a namespace and should use rolebinding (not a cluster role binding which is mentioned further in task) with namespace.
- Solution suggests to create a cluster role and cluster role binding, so it will have permissions to other namespaces.
But again, maybe this was an intention, so don’t care much about this task.