-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ghcr.io/hikhvar/mqtt2prometheus:v0.1.7-rc1 config file loading error #89
Labels
bug
Something isn't working
Comments
# Source: mqtt2prom/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: release-name-mqtt2prom
labels:
helm.sh/chart: mqtt2prom-0.1.0
app.kubernetes.io/name: mqtt2prom
app.kubernetes.io/instance: release-name
app.kubernetes.io/version: "0.1.0"
app.kubernetes.io/managed-by: Helm
spec:
replicas: 1
selector:
matchLabels:
app.kubernetes.io/name: mqtt2prom
app.kubernetes.io/instance: release-name
template:
metadata:
labels:
app.kubernetes.io/name: mqtt2prom
app.kubernetes.io/instance: release-name
spec:
securityContext:
{}
containers:
- args:
- /mqtt2prometheus
- -config
- /data/config.yaml
- -log-level
- debug
name: mqtt2prom
image: "ghcr.io/hikhvar/mqtt2prometheus:v0.1.6"
imagePullPolicy: Always
ports:
- name: http
containerPort: 9641
protocol: TCP
# livenessProbe:
# httpGet:
# path:
# port: http
# initialDelaySeconds: 45
# periodSeconds: 30
# readinessProbe:
# httpGet:
# path:
# port: http
# initialDelaySeconds: 45
# periodSeconds: 10
resources:
limits:
cpu: 100m
memory: 128Mi
requests:
cpu: 100m
memory: 128Mi
volumeMounts:
- name: mqtt2prom-config-secret-volume
mountPath: /data/config.yaml
subPath: config.yaml
readOnly: true
volumes:
- name: mqtt2prom-config-secret-volume
secret:
secretName: mqtt2prom-config-secret The config comes from a secret as the MQTT is password protected. |
Thank you for the feedback. Will look into it. Can't give a time frame yet. |
Ok, can reproduce your issue. I think this is relates to #84
If the leading
So I think, if you change your deployment to the following it should work again: # Source: mqtt2prom/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: release-name-mqtt2prom
labels:
helm.sh/chart: mqtt2prom-0.1.0
app.kubernetes.io/name: mqtt2prom
app.kubernetes.io/instance: release-name
app.kubernetes.io/version: "0.1.0"
app.kubernetes.io/managed-by: Helm
spec:
replicas: 1
selector:
matchLabels:
app.kubernetes.io/name: mqtt2prom
app.kubernetes.io/instance: release-name
template:
metadata:
labels:
app.kubernetes.io/name: mqtt2prom
app.kubernetes.io/instance: release-name
spec:
securityContext:
{}
containers:
- args:
- -config
- /data/config.yaml
- -log-level
- debug
name: mqtt2prom
image: "ghcr.io/hikhvar/mqtt2prometheus:v0.1.7-RC1"
imagePullPolicy: Always
ports:
- name: http
containerPort: 9641
protocol: TCP
# livenessProbe:
# httpGet:
# path:
# port: http
# initialDelaySeconds: 45
# periodSeconds: 30
# readinessProbe:
# httpGet:
# path:
# port: http
# initialDelaySeconds: 45
# periodSeconds: 10
resources:
limits:
cpu: 100m
memory: 128Mi
requests:
cpu: 100m
memory: 128Mi
volumeMounts:
- name: mqtt2prom-config-secret-volume
mountPath: /data/config.yaml
subPath: config.yaml
readOnly: true
volumes:
- name: mqtt2prom-config-secret-volume
secret:
secretName: mqtt2prom-config-secret |
No response, assume this is fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like
ghcr.io/hikhvar/mqtt2prometheus:v0.1.7-rc1
triggers the following error:Moving from
latest
tov0.1.6
image tag solved the problem.I can help with further debug but the config file should be there as the helm chart didn't change.
Thank you,
Radu
The text was updated successfully, but these errors were encountered: