juju k8s storage configuration
Bug #1814678 reported by
Ian Booth
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Ian Booth | ||
Bug Description
Juju deployed workloads on k8s need storage for:
- charm state in the operator pod
- workload state
Currently the user needs to configure the storage class (and hence provisioner) for both operator and workload storage. However, Juju can know what cloud the cluster is running on and use sensible defaults for the cluster so the user need only be asked to provide input if Juju cannot determine recommended cluster default storage.
eg on microk8s, there's always hostpath storage out of the box so this is what should be used by default
Maybe at 'add-k8s' time we could probably fail-to-add if we don't have a default storage or helpfully prompt the user at that point.
| tags: | added: k8s storage |
| tags: | added: realk |
| Changed in juju: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| status: | Triaged → In Progress |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
