Lab 6.1. RESTful API Access

@eporart I think it's because you simply copy-pasted following command from training material and didn't fix secret name.

export token=$(kubectl describe \
    secret default-token-jdqp7 |grep ˆtoken |cut -f7 -d' ')

You can just check if your token env variable is empty using command echo $token.

By the way I've just found that service account tokens are not automatically ambient in secrets in 1.24+. Thus if you want to have one you have to create it manually.

@eporart You just provided anonymous user with cluster-admin's role permission and opened a big security hole to your cluster...

In the same exercise, in my test deployment using kubeadm init/join, I was missing the bearer token, so I had to create that secret. Instructions here:

https://kubernetes.io/docs/tasks/administer-cluster/access-cluster-api/

Specifically:

# Create a secret to hold a token for the default service account
kubectl apply -f - <<EOF
apiVersion: v1
kind: Secret
metadata:
  name: default-token
  annotations:
    kubernetes.io/service-account.name: default
type: kubernetes.io/service-account-token
EOF

After that, the rest of the exercise worked.