use a reasonable default image
Bug #1892102 reported by
Paul Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charm-k8s-mattermost |
Triaged
|
Medium
|
Unassigned |
Bug Description
We should build a couple of images on rocks.canonical.com and have the charm use them by default.
When 'licence' is not set, we should use a Team Edition image.
When 'licence' is set, we should use an Enterprise Edition image.
However, we should retain the explicit image-related settings so that custom images can still be used.
Related branches
~pjdc/charm-k8s-mattermost/+git/charm-k8s-mattermost:default-image
- Haw Loeung: Approve
- Canonical IS Reviewers: Pending requested
-
Diff: 61 lines (+16/-7)2 files modifiedREADME.md (+15/-6)
config.yaml (+1/-1)
~pjdc/charm-k8s-mattermost/+git/image-build:build-flavours
Merged
into
~mattermost-charmers/charm-k8s-mattermost/+git/mattermost-k8s-image-builder:master
at
revision 67430a17ef017525cdc81bfa71ac81a119ed0371
- Haw Loeung: Approve (+1)
- Junien F: Approve
-
Diff: 102 lines (+47/-15)2 files modifiedDockerfile (+31/-13)
README.md (+16/-2)
Changed in charm-k8s-mattermost: | |
assignee: | Paul Collins (pjdc) → nobody |
To post a comment you must log in.
We're now building a vanilla image by default. I've created an OCI recipe on Launchpad to build and push a vanilla image, and updated the charm to use it.