[multus] change to use hostNetwork (#1250)

* use host network for multus daemonSet
This commit is contained in:
Jeffrey Borg 2021-10-18 20:08:33 +11:00 committed by GitHub
parent 4dc3408914
commit 5ccef0ec65
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 6 additions and 3 deletions

View File

@ -2,7 +2,7 @@ apiVersion: v2
appVersion: v3.7.1
description: multus CNI allows multiple NICs per pod
name: multus
version: 3.1.1
version: 3.1.2
kubeVersion: ">=1.16.0-0"
keywords:
- multus

View File

@ -1,6 +1,6 @@
# multus
![Version: 3.1.1](https://img.shields.io/badge/Version-3.1.1-informational?style=flat-square) ![AppVersion: v3.7.1](https://img.shields.io/badge/AppVersion-v3.7.1-informational?style=flat-square)
![Version: 3.1.2](https://img.shields.io/badge/Version-3.1.2-informational?style=flat-square) ![AppVersion: v3.7.1](https://img.shields.io/badge/AppVersion-v3.7.1-informational?style=flat-square)
multus CNI allows multiple NICs per pod

View File

@ -7,6 +7,9 @@ controller:
# -- deploy to all nodes
type: daemonset
# -- force hostnetwork so upgrades can't fail
hostNetwork: true
initContainers:
# -- Init container that installs reference CNI plugins
cni-installer:

View File

@ -7,7 +7,7 @@ metadata:
annotations:
# This is what defines this resource as a hook. Without this line, the
# job is considered part of the release.
"helm.sh/hook": pre-delete,pre-upgrade,pre-rollback
"helm.sh/hook": pre-delete
"helm.sh/hook-weight": "-5"
"helm.sh/hook-delete-policy": hook-succeeded
spec: