Unable to mount Kubernetes resources into pod
Bug #1858515 reported by
Kenneth Koski
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Yang Kelvin Liu |
Bug Description
I have a service that creates a Secret that then needs to get mounted into another pod for that service to work. Specifically, I have a certificate management service that will create a Secret containing a TLS certificate, which the second service then needs access to. It would be done in Kubernetes YAML with something like this:
volumes:
- name: config
configMap: # Or Secret
name: my-config-map
I don't see a way to do that within the current pod spec set v2.
Changed in juju: | |
milestone: | none → 2.8-beta1 |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: k8s |
Changed in juju: | |
assignee: | nobody → Yang Kelvin Liu (kelvin.liu) |
status: | Triaged → In Progress |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Similar situation here, I am trying to convert this type of yaml into a charm and I do not see how I can save the secret values directly into my pod environment variables.
apiVersion: apps/v1beta1
valueFrom:
secretKeyR ef:
kind: Deployment
metadata:
name: myapp-deployment
spec:
replicas: 1
template:
metadata:
labels:
app: myapp
spec:
containers:
- name: myapp
image: myapp:2017-latest
ports:
- containerPort: 1234
env:
- name: MYAPP_PASSWORD
name: myapp
key: PASSWORD