Q: 3
Create a Pod name Nginx-pod inside the namespace testing, Create a service for the Nginx-pod
named nginx-svc, using the ingress of your choice, run the ingress on tls, secure port.
Your Answer
Discussion
Create TLS secret first. Practice this flow with kubectl and review official CKS docs.
TLS secret first or the ingress won’t work. Trap is skipping that and trying to reference it before creation.
Is everyone remembering to generate the TLS certs and make the secret in the testing namespace before applying the ingress? Without that, ingress with TLS won't pick up the config right.
Yep, you always need to create the TLS secret before the ingress otherwise Kubernetes complains about a missing secret and the ingress won't go ready. The question specifically asks for TLS so that's required. Pretty sure this order matches what's expected but open if anyone knows a shortcut.
TLS secret has to be there before you apply the ingress, or else the ingress creation just fails since it tries to mount a non-existent secret. So sequence matters: secret, then pod/service, then ingress. Seen that issue in labs too, but maybe some controllers handle missing secrets differently?
Yeah, TLS secret must be created first in the testing namespace or ingress config for TLS will fail.
Why not make the TLS secret first, then build out the ingress? Saw a similar question on a practice and skipping the secret step is a common trap.
Definitely review the official CKS Kubernetes docs and try this in your own test cluster first.
Nah, you really need that TLS secret before creating the ingress or it'll just error out when it tries to reference a missing secret. Seen this trip people up on similar practice tasks. TLS order is a common trap.
Had something like this in a mock: TLS secret creation in the testing namespace first, then deploy manifests for pod, service, ingress.
Be respectful. No spam.
