values.yamlis required to deploy StackState with Helm. It contains your StackState license key, API key and other important information. The
generate_values.shscript in the installation directory of the Helm chart will guide you through generating the file.
generate_values.shscript in two ways:
-nto pass configuration on the command line, this is useful for scripting.
https://stackstate.internal. If you haven't decided on an Ingress configuration yet, use
http://localhost:8080. This can be updated later in the generated file.
admin) to access StackState's UI. This can be omitted from the command line, the script will prompt for it.
SecurityContextConfigurationobjects to the OpenShift installation.
chmodon their volumes and need to run with a specific (pre-known) UID.
SecurityContextConfigurationobjects in OpenShift. After that install the StackState Helm chart with the above flag set to
values.yamlfile and name it
helm installcommand. The agent chart also needs an additional
SecurityContextConfigurationobjects in OpenShift. Then ensure that you set the above configuration flag to
<CLUSTER_NAME>: A name that StackState will use to identify the cluster
<RANDOM_TOKEN>: A 32 character random token. This can be generated by executing
head -c32 < /dev/urandom | md5sum | cut -c-32
agent-values.yamland add it to the
helm installcommand to enable this feature.
openshift-values.yamlfile to deploy the latest StackState version to the
stackstatenamespace with the command below. If you want to automatically install the Cluster Agent for OpenShift, you will also require the
agent-values.yamlcreated in the previous step:
https://localhost:8080. Log in with the username
adminand the default password provided in the
hdfs-scc.yamland apply it as an administrator of the OpenShift cluster using the following command:
agent-scc.yamland apply it as an administrator of the OpenShift cluster using the following command: