Support for kubernetes hostPath Volumes

Bug #1861516 reported by George Kraft
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Yang Kelvin Liu

Bug Description

I'm trying to create a k8s charm for Multus, which requires the use of hostPath Volumes. For example, here's a snippet with the volumes and volumeMounts I'd like to include in the Deployment/DaemonSet:

containers:
- name: kube-multus
  image: nfvpe/multus:v3.4
  volumeMounts:
  - name: cni
    mountPath: /host/etc/cni/net.d
  - name: cnibin
    mountPath: /host/opt/cni/bin
volumes:
- name: cni
  hostPath:
    path: /etc/cni/net.d
- name: cnibin
  hostPath:
    path: /opt/cni/bin

As I understand it, this is currently not possible to do with pod-spec-set or metadata in k8s charms.

Tags: k8s
tags: added: k8s
Ian Booth (wallyworld)
Changed in juju:
milestone: none → 2.8-beta1
importance: Undecided → High
status: New → Triaged
Ian Booth (wallyworld)
Changed in juju:
assignee: nobody → Yang Kelvin Liu (kelvin.liu)
status: Triaged → Fix Committed
Revision history for this message
Yang Kelvin Liu (kelvin.liu) wrote :

hi George
This is supported in k8s spec v3 now.
Here is the doc: https://discourse.jujucharms.com/t/new-extended-volume-support-and-other-spec-v3-changes/2698

Harry Pidcock (hpidcock)
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.