Configure and Install Components Using Values Files
5 min
every installation in this guide can also be performed with a yaml values file instead of a chain of set flags this is the recommended approach for production, because the file can be version controlled, reviewed, and reused for upgrades long multi line commands are error prone if a space remains after a trailing backslash when the command is pasted into a terminal, the command breaks and helm reports errors such as “helm upgrade requires 2 arguments” using a values file avoids this class of error entirely agent — `agent values yaml` secrets installtoken "\<kron pam aapm agent installation token>" address "\<kron pam server address>" config singleconnect agentname "\<agent name>" sslignored false hostnameignored false then execute the following commands helm install kron aapm agent kron pam/kron aapm agent \\ \ namespace ns agent create namespace \\ f agent values yaml aapm service — `service values yaml` agent service "kron aapm agent ns agent svc cluster local" port "8080" ignorecertificate true interceptor ignorecertificate false pam url "https //\<kron pam server address>" vault allowedaccounts \ accountname "\<account name>" accountpath "\<account path>" then execute the following commands helm install aapm service kron pam/aapm service \\ \ namespace kron pam aapm create namespace \\ f service values yaml injector — `sidecar values yaml` namespace name ns sidecar aapmconnection agentservice "kron aapm agent ns agent svc cluster local" agentport "8080" directaccessurl "https //\<kron pam server address>" ignorecertificate true ignoreinterceptorcertificate false sidecarimage tag "\<verified image tag>" then execute the following commands helm install kron aapm sidecar kron pam/kron aapm sidecar \\ \ namespace ns sidecar create namespace \\ f sidecar values yaml values files contain installation tokens and kron pam access tokens store them with restricted permissions (chmod 600) and never commit them to a shared repository in plain text to review the values a release was actually installed with at any later point helm get values \<release name> n \<namespace> helm get values \<release name> n \<namespace> all