CKS Mock Exam 2 - Q2 enquiries

attempted Q9 of CKS Mock Exam 2, was able to create the ingress resource
Lab environment’s ingress controller doesn’t have a valid IP, test case is failing
I was able to have TLS enforced when curling rocket-server.local via the NodePort

root@controlplane ~ ➜ curl -k -v -H “Host: rocket-server.local” https://127.0.0.1:31550

  • Trying 127.0.0.1:31550…
  • Connected to 127.0.0.1 (127.0.0.1) port 31550 (#0)
  • ALPN, offering h2
  • ALPN, offering http/1.1
  • TLSv1.0 (OUT), TLS header, Certificate Status (22):
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
  • TLSv1.2 (IN), TLS header, Certificate Status (22):
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
  • TLSv1.2 (IN), TLS header, Finished (20):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.3 (IN), TLS handshake, Finished (20):
  • TLSv1.2 (OUT), TLS header, Finished (20):
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
  • SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
  • ALPN, server accepted to use h2
  • Server certificate:
  • subject: O=Acme Co; CN=Kubernetes Ingress Controller Fake Certificate
  • start date: Aug 2 13:59:55 2026 GMT
  • expire date: Aug 2 13:59:55 2027 GMT
  • issuer: O=Acme Co; CN=Kubernetes Ingress Controller Fake Certificate
  • SSL certificate verify result: self-signed certificate (18), continuing anyway.
  • Using HTTP2, server supports multiplexing
  • Connection state changed (HTTP/2 confirmed)
  • Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
  • Using Stream ID: 1 (easy handle 0x560f450e1a40)
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):

GET / HTTP/2
Host: rocket-server.local
user-agent: curl/7.81.0
accept: /

  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  • old SSL session ID is stale, removing
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
    < HTTP/2 200
    < date: Sun, 02 Aug 2026 14:23:44 GMT
    < content-type: text/html
    < content-length: 896
    < last-modified: Wed, 15 Jul 2026 16:03:14 GMT
    < etag: “6a57af42-380”
    < accept-ranges: bytes
    < strict-transport-security: max-age=15724800; includeSubDomains
    <
Welcome to nginx! html { color-scheme: light dark; } body { width: 35em; margin: 0 auto; font-family: Tahoma, Verdana, Arial, sans-serif; }

Welcome to nginx!

If you see this page, nginx is successfully installed and working. Further configuration is required for the web server, reverse proxy, API gateway, load balancer, content cache, or other features.

For online documentation and support please refer to nginx.org.
To engage with the community please visit community.nginx.org.
For enterprise grade support, professional services, additional security features and capabilities please refer to f5.com/nginx.

Thank you for using nginx.

* TLSv1.2 (IN), TLS header, Supplemental data (23): * Connection #0 to host 127.0.0.1 left intact

I just did this problem; part of the problem here is that the service for the IC is a LoadBalancer service which is in pending state – i.e., things are not set up correctly.

I tried the following which passed the grader, although I’m dubious about that:

  • I used the ClusterIP of the IC service for the rocket-server.local entry in hosts file
  • I used the solution for Q9 from the End Exam page.

I don’t think the ingress is working correctly, but it passes the grader. I’m going to create a ticket and ask the lab team what’s up with that.

Yeah, was wondering if it was a one-off thing, I reload the lab environment and the IC was still in Pending state for all the attempts.

Appreciate your help

The engineer pushed a fix today. Please give it a try; the service now resolves as a NodePort service, and has a valid external ID. That should do the trick.