-
Notifications
You must be signed in to change notification settings - Fork 36
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
Customise host path #94
Comments
Any update iam having my certificates in the host of the VM and iam having different paths instead of /etc. i added volumes and volumeMounts in the values.yaml but not reflecting inside the pod. |
#95 is an open PR so you can't configure volume mounts in the current release. I'll make sure to have a working version of it released soon. It would help a lot if you could test it out in your environment. I'll let you know asap. |
Just release image:
repository: ghcr.io/amimof/node-cert-exporter
pullPolicy: IfNotPresent
tag: "latest"
imagePullSecrets: []
paths:
- /host/etc/origin/node/
- /host/etc/origin/master/
- /host/etc/etcd/
- /host/etc/kubernetes/pki/
- /host/opts/certs
podAnnotations:
prometheus.io/scrape: "true"
prometheus.io/port: "9117"
tolerations:
# Allow running on masters:
- key: node-role.kubernetes.io/master
effect: NoSchedule
serviceAccount:
create: true
resources:
limits:
cpu: 250m
memory: 256Mi
requests:
cpu: 100m
memory: 128Mi
volumes:
- hostPath:
path: /etc
type: ""
name: etc
- hostPath:
path: /opt/certs
type: ""
name: opt-certs
volumeMounts:
- mountPath: /host/etc
name: etc
readOnly: true
- mountPath: /host/opt/certs
name: opt-certs
readOnly: true
|
Description
Allow support of parameterised value for host path in the daemonset.yaml instead of assuming that the certificates are always under /etc.
https://github.com/amimof/node-cert-exporter/blob/master/charts/node-cert-exporter/templates/daemonset.yaml
The text was updated successfully, but these errors were encountered: