Default bundle scale is "0"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned |
Bug Description
Hello,
Trying a new k8s charm with juju 2.8.1 and a bundle looking like this
bundle: kubernetes
applications:
mm-pd-bot:
charm: {{ charm_dir }}/mm-pd-bot
options:
image_path: stg-is.
mm_
tls_
# Those parameters are k8s specific
juju-
The result was a deployed application but no pod.
It took me some time to understand that I needed "scale: 1".
The only reference I could find was https:/
That's pretty confusing because usually, you want at least one pod for your application.
I would rather have a default to "scale: 1" and the possibility to set "scale: 0" if really needed.
What do you think ?
Changed in juju: | |
milestone: | 2.9-beta1 → 2.9-rc1 |
Changed in juju: | |
milestone: | 3.0.0 → 3.0.1 |
Changed in juju: | |
milestone: | 3.0.1 → 3.0.2 |
Changed in juju: | |
milestone: | 3.0.2 → 3.0.3 |
This sounds similar to the existing bug for max_units defaulting to 0, LP:1595330.