mirror of
https://github.com/kubernetes-sigs/node-feature-discovery.git
synced 2025-03-31 04:04:51 +00:00
Add NFD master '--instance' flag support to Helm chart
This commit is contained in:
parent
3e00bfb2ae
commit
88bd80d415
3 changed files with 6 additions and 1 deletions
|
@ -44,6 +44,10 @@ spec:
|
||||||
- "nfd-master"
|
- "nfd-master"
|
||||||
resources:
|
resources:
|
||||||
{{- toYaml .Values.master.resources | nindent 12 }}
|
{{- toYaml .Values.master.resources | nindent 12 }}
|
||||||
|
args:
|
||||||
|
{ { - if .Values.master.instance | empty | not } }
|
||||||
|
- "--instance={{ .Values.master.instance }}"
|
||||||
|
{ { - end } }
|
||||||
## Enable TLS authentication
|
## Enable TLS authentication
|
||||||
## The example below assumes having the root certificate named ca.crt stored in
|
## The example below assumes having the root certificate named ca.crt stored in
|
||||||
## a ConfigMap named nfd-ca-cert, and, the TLS authentication credentials stored
|
## a ConfigMap named nfd-ca-cert, and, the TLS authentication credentials stored
|
||||||
|
@ -51,7 +55,6 @@ spec:
|
||||||
## Additional hardening can be enabled by specifying --verify-node-name in
|
## Additional hardening can be enabled by specifying --verify-node-name in
|
||||||
## args, in which case every nfd-worker requires a individual node-specific
|
## args, in which case every nfd-worker requires a individual node-specific
|
||||||
## TLS certificate.
|
## TLS certificate.
|
||||||
# args:
|
|
||||||
# - "--ca-file=/etc/kubernetes/node-feature-discovery/trust/ca.crt"
|
# - "--ca-file=/etc/kubernetes/node-feature-discovery/trust/ca.crt"
|
||||||
# - "--key-file=/etc/kubernetes/node-feature-discovery/certs/tls.key"
|
# - "--key-file=/etc/kubernetes/node-feature-discovery/certs/tls.key"
|
||||||
# - "--cert-file=/etc/kubernetes/node-feature-discovery/certs/tls.crt"
|
# - "--cert-file=/etc/kubernetes/node-feature-discovery/certs/tls.crt"
|
||||||
|
|
|
@ -19,6 +19,7 @@ nameOverride: ""
|
||||||
fullnameOverride: ""
|
fullnameOverride: ""
|
||||||
|
|
||||||
master:
|
master:
|
||||||
|
instance:
|
||||||
replicaCount: 1
|
replicaCount: 1
|
||||||
|
|
||||||
podSecurityContext: {}
|
podSecurityContext: {}
|
||||||
|
|
|
@ -171,6 +171,7 @@ We have introduced the following Chart parameters.
|
||||||
##### Master pod parameters
|
##### Master pod parameters
|
||||||
|
|
||||||
| `master.*` | dict | | NFD master deployment configuration |
|
| `master.*` | dict | | NFD master deployment configuration |
|
||||||
|
| `master.instance` | string | | Instance name. Used to separate annotation namespaces for multiple parallel deployments |
|
||||||
| `master.replicaCount` | integer | 1 | Number of desired pods. This is a pointer to distinguish between explicit zero and not specified |
|
| `master.replicaCount` | integer | 1 | Number of desired pods. This is a pointer to distinguish between explicit zero and not specified |
|
||||||
| `master.podSecurityContext` | dict | {} | SecurityContext holds pod-level security attributes and common container settings |
|
| `master.podSecurityContext` | dict | {} | SecurityContext holds pod-level security attributes and common container settings |
|
||||||
| `master.service.type` | string | ClusterIP | NFD master service type |
|
| `master.service.type` | string | ClusterIP | NFD master service type |
|
||||||
|
|
Loading…
Add table
Reference in a new issue