This chart is DEPRECATED and moved to https://github.com/appscode/charts
Kubed by AppsCode - A Kubernetes cluster manager daemon.
$ helm install stable/kubed
This chart bootstraps a Kubed controller deployment on a Kubernetes cluster using the Helm package manager.
- Kubernetes 1.7+
To install the chart with the release name my-release
:
$ helm install stable/kubed --name my-release
The command deploys Kubed operator on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.
Tip: List all releases using
helm list
To uninstall/delete the my-release
:
$ helm delete my-release
The command removes all the Kubernetes components associated with the chart and deletes the release.
The following table lists the configurable parameters of the Kubed chart and their default values.
Parameter | Description | Default |
---|---|---|
replicaCount |
Number of kubed operator replicas to create (only 1 is supported) | 1 |
image |
container image | appscode/kubed |
tag |
container image tag | 0.4.0 |
imagePullSecrets |
Specify image pull secrets | nil (does not add image pull secrets to deployed pods) |
imagePullPolicy |
Image pull policy | IfNotPresent |
criticalAddon |
If true, installs kubed operator as critical addon | false |
logLevel |
Log level for kubed | 3 |
nodeSelector |
Node labels for pod assignment | {} |
rbac.create |
install required rbac service account, roles and rolebindings | false |
rbac.serviceAccountName |
ServiceAccount Kubed will use (ignored if rbac.create=true) | default |
Specify each parameter using the --set key=value[,key=value]
argument to helm install
. For example:
$ helm install --name my-release --set image.tag=v0.2.1 stable/kubed
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example:
$ helm install --name my-release --values values.yaml stable/kubed
By default the chart will not install the recommended RBAC roles and rolebindings.
You need to have the flag --authorization-mode=RBAC
on the api server. See the following document for how to enable RBAC.
To determine if your cluster supports RBAC, run the following command:
$ kubectl api-versions | grep rbac
If the output contains "beta", you may install the chart with RBAC enabled (see below).
To enable the creation of RBAC resources (On clusters with RBAC). Do the following:
$ helm install --name my-release stable/kubed --set rbac.create=true