-
-
Notifications
You must be signed in to change notification settings - Fork 25
/
Copy pathREADME.md.gotmpl
84 lines (56 loc) · 2.23 KB
/
README.md.gotmpl
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
{{ template "chart.header" . }}
{{ template "chart.description" . }}
## TL;DR;
```console
helm repo add christianhuth https://charts.christianhuth.de
helm repo update
helm install my-release christianhuth/node-access
```
## Introduction
This chart bootstraps one or multiple Pods to access the host system of a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
## Prerequisites
- Kubernetes 1.19+
## Installing the Chart
To install the chart with the release name `my-release`:
```console
helm repo add christianhuth https://charts.christianhuth.de
helm repo update
helm install my-release christianhuth/node-access
```
These commands deploys one or multiple Pods to access the host system of the Kubernetes cluster in the default configuration. The [Values](#values) section lists the values that can be configured during installation.
> **Tip**: List all releases using `helm list`
## Uninstalling the Chart
To uninstall the `my-release` deployment:
```console
helm uninstall my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
{{ template "chart.valuesSection" . }}
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml christianhuth/node-access
```
## Deploying to a specific Node
If you want to deploy only to one specific Node you can simply define the `nodeName` using `--set nodeAccess.nodePlacement.nodeName=<NODE_NAME>` or through the values file:
```yaml
nodeAccess:
accessMode: deployment
nodePlacement:
nodeName: <NODE_NAME>
```
## Deploying to all Nodes
If you want to deploy Pods to access all Nodes, the easiest way is to use a DaemonSet instead of a Deployment using `--set nodeAccess.accessMode="daemonset"` or through the values file:
```yaml
nodeAccess:
accessMode: daemonset
```
## Deploying to a subset of Nodes
If you want to deploy Pods to a subset of Nodes you can use a DaemonSet and a NodeSelector:
```yaml
nodeAccess:
accessMode: daemonset
nodePlacement:
nodeSelector:
key: value
```