Welcome to the Linux Foundation Forum!

Chapter 11 is outdated and should be replaced.

E.g., kubectl run creates a pod not a deployment. Just one example.

Comments

  • fcioanca
    fcioanca Posts: 2,437

    This command has been updated.

  • And there are in fact sections on the Gateway API.

  • Are we supposed to actually be able to run the manifests and execute the steps in the class notes or just wait for the lab itself?
    There are problems with the simple ingress resource configuration 1) typo 2) old conventions 3) relying on a single ingress controller being installed.:

    apiVersion: networking.k8s.io/v1 
    kind: Ingress 
    metadata:
      name: ghost-ingress
    spec:
    **# missing something like: ingressClassName: nginx**
      rules:
      - host: ghost.192.168.99.100.nip.io
        http:
          paths:
          - path: /
            pathType: ImplementationSpecific  # <-- should be Prefix
            backend:
             ** service  # <--- missing colon**
                name: ghost
                port:
                  number: 2368
    
  • And the host: should be "ghost..nip.io. The IP address in the example looks to be the one for minikube.

  • chrispokorni
    chrispokorni Posts: 2,577

    Hi @sfleisch314,

    Thank you for reporting the missing colon typo. It has been fixed.

    The code snippets or manifest examples in lectures may not include all possible options and variants. That is why optional entries can be omitted (such as the ingressClassName), while more generic values (for the pathType) and host addresses (the non-Minikube specific private IP) could be presented.

    Regards,
    -Chris

Categories

Upcoming Training