From 53e4b40d02159025e5addfc9fb70fd9dfee426d0 Mon Sep 17 00:00:00 2001 From: Jiayi Hu Date: Mon, 11 Jan 2021 18:12:38 +0100 Subject: [PATCH] Favour inline set flags to values.yaml --- docs/user-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide.md b/docs/user-guide.md index 583958a66..1272eb148 100644 --- a/docs/user-guide.md +++ b/docs/user-guide.md @@ -100,7 +100,7 @@ helm install akri akri-helm-charts/akri However, control plane nodes on MicroK8s and K3s may not have this exact label by default, so you can add it by running `kubectl label node ${HOSTNAME,,} node-role.kubernetes.io/master= - --overwrite=true`. Or alternatively, in K3s, you can set `controllers.nodeSelectors` to `"node-role.kubernetes.io/master": "true"` using a `values.yaml` file and passing `--set values.yaml` to the install command below. Any other `--set` flag mentioned so far can also be written in `values.yaml` as described in [Helm Value Files documentation](https://helm.sh/docs/chart_template_guide/values_files/). + --overwrite=true`. Or alternatively, in K3s, you can keep the default label value on the master and add `--set controller.nodeSelectors."node-role\.kubernetes\.io/master"=true` to the install command below. Run the following to fetch the Akri Helm chart, install Akri, and apply the default configuration for ``, optionally specifying the image for the broker pod that should be deployed to utilize each discovered device.