hostNetwork for k8s charms
Bug #1933677 reported by
Konstantinos Tsakalozos
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
While charming a home automation software (openhab) I saw that some of its functionality depends on the container being on the the host's network stack, eg UPnP discovery [1].
Do you think this is something we could have?
summary: |
- hosNetwork for k8s charms + hostNetwork for k8s charms |
Changed in juju: | |
milestone: | 2.9-next → 3.1-beta1 |
Changed in juju: | |
milestone: | 3.1-beta1 → 3.2-beta1 |
Changed in juju: | |
milestone: | 3.2-beta1 → 3.2-rc1 |
Changed in juju: | |
milestone: | 3.2-rc1 → 3.2.0 |
Changed in juju: | |
milestone: | 3.2.0 → 3.2.1 |
Changed in juju: | |
milestone: | 3.2.1 → 3.2.2 |
Changed in juju: | |
milestone: | 3.2.2 → 3.2.3 |
Changed in juju: | |
milestone: | 3.2.3 → 3.2.4 |
Changed in juju: | |
milestone: | 3.2.4 → 3.2.5 |
tags: | added: k8s |
Changed in juju: | |
milestone: | 3.2.5 → none |
To post a comment you must log in.
This is currently supported in v1 operator style charms using pod-spec-set
pod:
hostNetwork: true
But not yet in sidecar charms