为什么/var/run/secrets/kubernetes.io/serviceaccount/token在Pod中会是一个空文件?

问题描述

我正在使用香草minikube环境.

I'm using a vanilla minikube environment.

我没有在简单的Pod .yaml简单文件中指定任何与服务帐户相关的说明.

I'm not specifying any service account-related instructions in my bare-bones simple Pod .yaml file.

在已部署的Pod中，/var/run/secrets/kubernetes.io/serviceaccount/token为空.可能的原因是什么?

Inside a deployed Pod, /var/run/secrets/kubernetes.io/serviceaccount/token is empty. What are the possible causes for this?

推荐答案

如上所述在文档中

apiVersion: v1
kind: ServiceAccount
metadata:
  name: build-robot
automountServiceAccountToken: false

apiVersion: v1
kind: Pod
metadata:
  name: my-pod
spec:
  serviceAccountName: build-robot
  automountServiceAccountToken: false

因此，请仔细检查您的pod文件，并使用以下命令检查您的ServiceAccount配置kubectl describe serviceaccount build-robot查看是否要禁用自动挂载.

So double check your pod file and check your ServiceAccount configuration withkubectl describe serviceaccount build-robot to see if you are disabling the automount.

这篇关于为什么/var/run/secrets/kubernetes.io/serviceaccount/token在Pod中会是一个空文件?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！