在我的Python中无法访问Kubernetes env var初始py金融机构

Question

我在python应用程序中访问Kubernetes环境变量时遇到问题初始py文件。不过，它似乎在其他文件中可用。在

我的初始py文件包含以下代码app.config.from_object(os.environ['APP_SETTINGS'])。APP_SETTINGS的值取决于我的环境，其值为config.DevelopmentConfig、config.StagingConfig或{}。从这里，我的应用程序从我的配置.py文件，如下所示：

import os
basedir = os.path.abspath(os.path.dirname(__file__))

class Config(object):
  WTF_CSRF_ENABLED = True
  SECRET_KEY = 'you-will-never-guess'
  APP_SETTINGS = os.environ['APP_SETTINGS'] # For debug purposes


class DevelopmentConfig(Config):
  TEMPLATES_AUTO_RELOAD = True
  DEBUG = True

class StagingConfig(Config):
  DEBUG = True

class ProductionConfig(Config):
  DEBUG = False

当我在docker compose的开发环境中本地设置APP_设置时，比如。。。在

^{pr2}$

一切正常。当我在我的Secrets文件中设置了APP_SETTINGS=config.StagingConfig部署到Kubernetes中的登台舱时，会出现以下错误：

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/werkzeug/utils.py", line 434, in import_string
    return getattr(module, obj_name)
AttributeError: module 'config' has no attribute 'StagingConfig
'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/werkzeug/utils.py", line 436, in import_string
    raise ImportError(e)
ImportError: module 'config' has no attribute 'StagingConfig
'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "manage.py", line 3, in <module>
    from app import app
  File "/root/app/__init__.py", line 11, in <module>
    app.config.from_object(os.environ['APP_SETTINGS'])
  File "/usr/local/lib/python3.6/site-packages/flask/config.py", line 168, in from_object
    obj = import_string(obj)
  File "/usr/local/lib/python3.6/site-packages/werkzeug/utils.py", line 443, in import_string
    sys.exc_info()[2])
  File "/usr/local/lib/python3.6/site-packages/werkzeug/_compat.py", line 137, in reraise
    raise value.with_traceback(tb)
  File "/usr/local/lib/python3.6/site-packages/werkzeug/utils.py", line 436, in import_string
    raise ImportError(e)
werkzeug.utils.ImportStringError: import_string() failed for 'config.StagingConfig\n'. Possible reasons are:
- missing __init__.py in a package;
- package or module path not included in sys.path;
- duplicated package or module name taking precedence in sys.path;
- missing module, class, function or variable;
Debugged import:
- 'config' found in '/root/config.py'.
- 'config.StagingConfig\n' not found.
Original exception:
ImportError: module 'config' has no attribute 'StagingConfig
'
upgrading database schema...
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/werkzeug/utils.py", line 434, in import_string
    return getattr(module, obj_name)
AttributeError: module 'config' has no attribute 'StagingConfig
'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/werkzeug/utils.py", line 436, in import_string
    raise ImportError(e)
ImportError: module 'config' has no attribute 'StagingConfig
'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "manage.py", line 3, in <module>
    from app import app
  File "/root/app/__init__.py", line 11, in <module>
    app.config.from_object(os.environ['APP_SETTINGS'])
  File "/usr/local/lib/python3.6/site-packages/flask/config.py", line 168, in from_object
    obj = import_string(obj)
  File "/usr/local/lib/python3.6/site-packages/werkzeug/utils.py", line 443, in import_string
    sys.exc_info()[2])
  File "/usr/local/lib/python3.6/site-packages/werkzeug/_compat.py", line 137, in reraise
    raise value.with_traceback(tb)
  File "/usr/local/lib/python3.6/site-packages/werkzeug/utils.py", line 436, in import_string
    raise ImportError(e)
werkzeug.utils.ImportStringError: import_string() failed for 'config.StagingConfig\n'. Possible reasons are:
- missing __init__.py in a package;
- package or module path not included in sys.path;
- duplicated package or module name taking precedence in sys.path;
- missing module, class, function or variable;
Debugged import:
- 'config' found in '/root/config.py'.
- 'config.StagingConfig\n' not found.
Original exception:
ImportError: module 'config' has no attribute 'StagingConfig
'
starting metriculous web server...
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/werkzeug/utils.py", line 434, in import_string
    return getattr(module, obj_name)
AttributeError: module 'config' has no attribute 'StagingConfig
'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/werkzeug/utils.py", line 436, in import_string
    raise ImportError(e)
ImportError: module 'config' has no attribute 'StagingConfig
'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "manage.py", line 3, in <module>
    from app import app
  File "/root/app/__init__.py", line 11, in <module>
    app.config.from_object(os.environ['APP_SETTINGS'])
  File "/usr/local/lib/python3.6/site-packages/flask/config.py", line 168, in from_object
    obj = import_string(obj)
  File "/usr/local/lib/python3.6/site-packages/werkzeug/utils.py", line 443, in import_string
    sys.exc_info()[2])
  File "/usr/local/lib/python3.6/site-packages/werkzeug/_compat.py", line 137, in reraise
    raise value.with_traceback(tb)
  File "/usr/local/lib/python3.6/site-packages/werkzeug/utils.py", line 436, in import_string
    raise ImportError(e)
werkzeug.utils.ImportStringError: import_string() failed for 'config.StagingConfig\n'. Possible reasons are:
- missing __init__.py in a package;
- package or module path not included in sys.path;
- duplicated package or module name taking precedence in sys.path;
- missing module, class, function or variable;
Debugged import:
- 'config' found in '/root/config.py'.
- 'config.StagingConfig\n' not found.
Original exception:
ImportError: module 'config' has no attribute 'StagingConfig

但是，当我在初始py像这样的文件app.config.from_object('config.StagingConfig')并部署到Kubernetes，它工作得很好。当我这样做时，我甚至可以通过登录我的pod并运行echo $APP_SETTINGS来确认我在Kubernetes的设置中声明的APP_SETTINGS env var是否存在。在

你觉得我做错什么了吗？在

编辑#1-添加我的部署.yaml文件

kind: Deployment
apiVersion: apps/v1beta2
metadata:
  annotations:
    deployment.kubernetes.io/revision: '4'
  selfLink: /apis/apps/v1beta2/namespaces/tools/deployments/met-staging-myapp
  resourceVersion: '51731234'
  name: met-staging-myapp
  uid: g1fce905-1234-56y4-9c15-12de61100d0a
  creationTimestamp: '2018-01-29T17:22:14Z'
  generation: 6
  namespace: tools
  labels:
    app: myapp
    chart: myapp-1.0.1
    heritage: Tiller
    release: met-staging
spec:
  replicas: 1
  selector:
    matchLabels:
      app: myapp
      release: met-staging
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: myapp
        release: met-staging
    spec:
      containers:
        - name: myapp-web
          image: 'gitlab.ourdomain.com:4567/ourspace/myapp:web-latest'
          ports:
            - containerPort: 80
              protocol: TCP
          env:
            - name: APP_SETTINGS
              valueFrom:
                secretKeyRef:
                  name: myapp-creds
                  key: APP_SETTINGS
            - name: AWS_ACCESS_KEY_ID
              valueFrom:
                secretKeyRef:
                  name: myapp-creds
                  key: AWS_ACCESS_KEY_ID
            - name: AWS_SECRET_ACCESS_KEY
              valueFrom:
                secretKeyRef:
                  name: myapp-creds
                  key: AWS_SECRET_ACCESS_KEY
          resources: {}
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
          imagePullPolicy: Always
        - name: myapp-celery
          image: 'gitlab.ourdomain.com:4567/ourspace/myapp:celery-latest'
          env:
            - name: APP_SETTINGS
              valueFrom:
                secretKeyRef:
                  name: myapp-creds
                  key: APP_SETTINGS
            - name: AWS_ACCESS_KEY_ID
              valueFrom:
                secretKeyRef:
                  name: myapp-creds
                  key: AWS_ACCESS_KEY_ID
            - name: AWS_SECRET_ACCESS_KEY
              valueFrom:
                secretKeyRef:
                  name: myapp-creds
                  key: AWS_SECRET_ACCESS_KEY
          resources: {}
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
          imagePullPolicy: Always
        - name: rabbit
          image: 'rabbitmq:alpine'
          env:
            - name: RABBITMQ_DEFAULT_USER
              value: rabbit_user
            - name: RABBITMQ_DEFAULT_PASS
              value: fake_pw
          resources: {}
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
          imagePullPolicy: IfNotPresent
      restartPolicy: Always
      terminationGracePeriodSeconds: 30
      dnsPolicy: ClusterFirst
      securityContext: {}
      imagePullSecrets:
        - name: gitlab-registry
      schedulerName: default-scheduler
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxUnavailable: 1
      maxSurge: 1
  revisionHistoryLimit: 10
  progressDeadlineSeconds: 600
status:
  observedGeneration: 6
  replicas: 1
  updatedReplicas: 1
  readyReplicas: 1
  availableReplicas: 1
  conditions:
    - type: Available
      status: 'True'
      lastUpdateTime: '2018-01-29T17:22:14Z'
      lastTransitionTime: '2018-01-29T17:22:14Z'
      reason: MinimumReplicasAvailable
      message: Deployment has minimum availability.
    - type: Progressing
      status: 'True'
      lastUpdateTime: '2018-05-25T10:20:49Z'
      lastTransitionTime: '2018-02-16T20:29:45Z'
      reason: NewReplicaSetAvailable
      message: >-
        ReplicaSet "met-staging-myapp-2615c4545f" has successfully
        progressed.

Answer 1

werkzeug.utils.ImportStringError: import_string() failed for 'config.StagingConfig\n'. Possible reasons are:

它非常清楚地向您展示了模块名后面有一个换行符，对于那些试图echo something | base64并将该值放入kubernetesSecret的人来说，这是一个非常非常常见的错误。这是正确的。或者，当然，停止将非机密文本放入机密中，使用ConfigMap或仅使用传统环境value: config.StagingConfig设置，并为Secret值保留{}构造。在