kubernetes - 配置映射不适用于 Pod?

标签 kubernetes

我反复看到类似的东西;

Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "some-service" with RunContainerError: "GenerateRunContainerOptions: Couldn't find key app-id in ConfigMap default/intercom"



部署尝试设置 env 的位置。来自配置映射的变量,即:
apiVersion: v1
data:
  intercom: |
    app-id=some-id
    api-key=some-key
kind: ConfigMap
metadata:
  creationTimestamp: 2016-10-23T13:09:58Z
  name: intercom
  namespace: default
  resourceVersion: "3836"
  selfLink: /api/v1/namespaces/default/configmaps/intercom
  uid: ffeea5f0-9921-11e6-b2b7-0acff65e44c3

部署看起来像:
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: myservice
spec:
  replicas: 2
  template:
    metadata:
     labels:
        run: myservice
    spec:
      containers:
        - name: myservice
          image: somerepo/myservice:v1.0
          env:
            - name: INTERCOM_APPID
              valueFrom:
                configMapKeyRef:
                  name: intercom
                  key: app-id
            - name: INTERCOM_APIKEY
              valueFrom:
                configMapKeyRef:
                  name: intercom
                  key: api-key
          ports:
            - containerPort: 9000
      imagePullSecrets:
        - name: docker-hub-key

这里可能有什么问题?

最佳答案

您的配置映射仅包含一个键:intercom

关于kubernetes - 配置映射不适用于 Pod?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/40203624/

相关文章:

docker - Kubernetes - 通过 ssh 连接到远程数据库服务器

ubuntu - Kubernetes kube-dns pod 待定

dns - 微服务的kubernetes dns查找

jenkins - 什么可能导致 Kubernetes Jenkins 从 pod 启动和暂停

kubernetes - 从 Minikube 内部调用外部服务

azure - Azure AKS 的 aci-connector-linux pod 处于 CrashLoopBackOff 状态

kubernetes - 将Pod调度到节点中时,k8是否考虑 'requested'或 'limit'资源?

kubernetes - Helm升级超时,无法获取配置映射

kubernetes - 版本 "AdmissionConfiguration"中的种类 "apiserver.config.k8s.io/v1"没有匹配项

azure - 将 ado 变量传递给 Azure ADO 上的 pv、pvc、配置映射和部署文件