Welcome to the Linux Foundation Forum!

Lab 6.3 does not show service account at step 11

Posts: 3
in LFD259 Class Forum

Hi,
trying to complete the lab exercise on ServiceAccounts, does not show serviceaccounts as described in Step 11. I checked all the previous steps look good. COuld please help here if i am missing anything here? My secondapp.yaml FYR:

  1. apiVersion: v1
  2. kind: Pod
  3. metadata:
  4.   name: secondapp
  5. spec:
  6.   serviceAccountName: secret-access-sa
  7.   securityContext:
  8.     runAsUser: 1000
  9.   containers:
  10.   - name: busy
  11.     image: busybox
  12.     command:
  13.       - sleep
  14.       - "3600"
  15.     securityContext:
  16.       runAsUser: 2000
  17.       allowPrivilegeEscalation: false
  18.       capabilities:
  19.         add: ["NET_ADMIN","SYS_TIME"]
  20.     volumeMounts:
  21.     - name: mysql
  22.       mountPath: /mysqlpassword
  23.   volumes:
  24.   - name: mysql
  25.     secret:
  26.       secretName: lfsecret

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Comments

  • Posts: 3
    edited August 2021

    I'm getting the same bad results that show kube-api-access-xxxxx instead of secret-access-sa-token-xxxxx or default-token-xxxxx (like the "before" example shows). I wiped things and tried a second time with no change.

    1. $ kubectl describe pod secondapp | grep -i secret
    2.       /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-5ncf7 (ro)
    3.     Type:        Secret (a volume populated by a Secret)
    4.     SecretName:  lfsecret
  • Posts: 2,453

    Hi,

    Thank you for your feedback. I started investigating the issues, and after preliminary testing I am suspecting an admission controller that may be required but is not accepted by the apiserver when reconfigured. I will keep looking into it.

    Regards,
    -Chris

  • Posts: 4

    Hi,

    I am having the same issue as well.

    Thanks.

  • Posts: 3

    I am having the same issue too

  • Posts: 3
    edited September 2021

    Unfortunately, at this point it seems that the course material is either broken or out of date. I wouldn't recommend waiting for a solution. I had to just move on with the course.

  • Posts: 1,000

    Thanks for the information. I'll work on updating the material today.

    As you are aware, Kubernetes is a dynamic subject. The constant change does lead to hiccups.

    Regards,

  • Posts: 3

    Yes, I am aware that Kubernetes is regularly changing. That's part of why I paid for the course and used the exact distro and install processes it recommended.

    My frustration wasn't that an issue cropped up, but that it went weeks unresolved. Doing the course work on my own time after work, trying this unsuccessfully multiple times cost me a lot of time.

  • Posts: 1
    edited October 2021

    Apparently it's still broken. Exactly the same problem happens to me :|. Any help or contribution I would be very grateful

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Quick Links

Categories

Upcoming Training