oc
)stackstate
:helm
and kubectl
commands as the namespace name in the --namespace
flagvalues.yaml
values.yaml
is required to deploy StackState with Helm. It contains your StackState license key, API key and other important information. The generate_values.sh
script in the installation directory of the Helm chart will guide you through generating the file.helm repo update
.generate_values.sh
script in two ways:-n
to pass configuration on the command line, this is useful for scripting.-b
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.-u
-p
-l
-a
-d
admin
) to access StackState's UI. This can be omitted from the command line, the script will prompt for it.-k
values.yaml
file somewhere safe. You can reuse this file for upgrades, which will save time and (more importantly) will ensure that StackState continues to use the same API key. This is desirable as it means agents and other data providers for StackState will not need to be updated.SecurityContextConfiguration
objects to the OpenShift installation.hbase.hdfs.scc.enabled
chmod
on their volumes and need to run with a specific (pre-known) UID.SecurityContextConfiguration
objects in OpenShift. After that install the StackState Helm chart with the above flag set to false
.values.yaml
file and name it openshift-values.yaml
.helm install
command. The agent chart also needs an additional SecurityContextConfiguration
on OpenShift.cluster-agent.agent.scc.enabled
SecurityContextConfiguration
objects in OpenShift. Then ensure that you set the above configuration flag to false
.<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.yaml
and add it to the helm install
command to enable this feature.values.yaml
and copied openshift-values.yaml
file to deploy the latest StackState version to the stackstate
namespace with the command below. If you want to automatically install the Cluster Agent for OpenShift, you will also require the agent-values.yaml
created in the previous step:https://localhost:8080
. Log in with the username admin
and the default password provided in the values.yaml
file.SecurityContextConfiguration
objectsSecurityContextConfiguration
objects.hdfs-scc.yaml
and apply it as an administrator of the OpenShift cluster using the following command:SecurityContextConfiguration
object:SecurityContextConfiguration
needs to be applied:agent-scc.yaml
and apply it as an administrator of the OpenShift cluster using the following command:SecurityContextConfiguration
object: