Improve placement / constraints modeling for k8s charms: tolerances, and affinity / anti-affinity
Bug #1895887 reported by
Cory Johns
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
In addition to nodeSelectors, Kubernetes supports tolerations and affinity / anti-affinity to influence scheduling pods to nodes. Tolerations in particular are important for setups where certain nodes should be reserved for system-level services and thus have taints on them to prevent scheduling normal pods, which can be selectively overridden by tolerations on the pod spec. We've already had at least one request to adjust tolerations for a cdk-addon which is currently being converted to a K8s charm.
Changed in juju: | |
milestone: | none → 2.9-beta1 |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju: | |
milestone: | 2.9-beta1 → 2.9-rc1 |
tags: | added: seg |
tags: | added: sts |
To post a comment you must log in.
Also, in line with https:/ /bugs.launchpad .net/juju/ +bug/1893123 it would be important for the charm to be able to specify default values for the ones modeled by placement.