我在访问python应用程序的init.py文件中的Kubernetes环境变量时遇到问题。然而，它似乎在其他文件中可用。
我的init.py文件包括这个代码app.config.from_object(os.environ['APP_SETTINGS'])。APP_SETTINGS的值取决于我的环境，值为config.DevelopmentConfig、config.StagingConfig或config.ProductionConfig。从这里，我的应用程序从我的config.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_SETTINGS时，就像这样…
environment:
- APP_SETTINGS=config.DevelopmentConfig
一切都很好。当我在我的Secrets文件中设置了APP_SETTINGS=config.StagingConfig并部署到Kubernetes中的Staging pod时，我会遇到以下错误：
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.StagingConfign'. 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.StagingConfign' 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.StagingConfign'. 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.StagingConfign' 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.StagingConfign'. 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.StagingConfign' not found.
Original exception:
ImportError: module 'config' has no attribute 'StagingConfig
然而，当我像app.config.from_object('config.StagingConfig')一样在init.py文件中硬编码APP_SETTINGS值并部署到Kubernetes时，它工作得很好。当我这样做的时候，我甚至可以通过登录我的pod并运行echo $APP_SETTINGS来确认我在Kubernetes中的设置中声明的APP_SETTINGS env var是否存在。
有没有想过我做错了什么？
编辑#1-添加我的deployment.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.
werkzeug.utils.ImportStringError: import_string() failed for 'config.StagingConfign'. Possible reasons are:
它非常清楚地向您显示，模块名称有一个尾随换行符，这对于尝试echo something | base64并将该值放入kubernetesSecret的人来说是一个非常、非常、非常常见的错误。正确的方法是通过kubectl create secret generic myapp-creds --from-literal=APP_SETTINGS=config.StagingConfig或printf '%s' config.StagingConfig | base64。当然，也可以停止将非Secret文本放入Secret并使用ConfigMap或仅使用传统环境value: config.StagingConfig设置，并为Secret值保留Secret构造。