Installation

once you have a new k8s cluster created as per the guidelines provided in the cluster requirements doc, installing any opsverse stack can be done using the following steps first time installation download config generator download the config generator \# linux amd64 https //opsverse public s3 amazonaws com/self host/latest/opsverse config generator linux amd64 \# linux arm64 https //opsverse public s3 amazonaws com/self host/latest/opsverse config generator linux arm64 \# osx amd64 https //opsverse public s3 amazonaws com/self host/latest/opsverse config generator darwin amd64 \# osx arm64 https //opsverse public s3 amazonaws com/self host/latest/opsverse config generator darwin arm64 \# windows amd64 https //opsverse public s3 amazonaws com/self host/latest/opsverse config generator windows amd64 exe run the config generator run the following command and follow instructions on your screen /opsverse config generator \<os> \<architecture> at the end of the process, you will be presented with two values yaml files, which will be preconfigured with all the base configurations required for installing your opsverse stack save this values yaml file since it will contain all the configuration for your opsverse stack and will be required when you want to update components/versions or upgrade observenow components it can also be committed to git if you want to follow a gitops workflow install the operators install the operators required for your stack by running the following helm install against your cluster with one of the config files generated in the previous step helm upgrade install operators now n observe create namespace opsverse operators repo https //\<username> \<password>@registry devopsnow\ io/chartrepo/internal f operator values yaml make sure to replace username/password above with the credentials you have received from your opsverse onboarding representative install the stack installing your opsverse stack is now simply a matter of running helm install against your cluster with the other config file generated in the previous step helm upgrade install \<custname> \<stackname> n observe create namespace opsverse onow repo https //\<username> \<password>@registry devopsnow\ io/chartrepo/internal f values yaml make sure to replace username/password above with the credentials you have received from your opsverse onboarding representative that's it! if you look at your cluster, you should see opsverse components coming up give it a few minutes to ensure all pods are up and running add dns entries the helm command should also give a list of ingresses created that need to be added to your dns service ( eg route53 ) you can also run kubectl get ingress a to get a list of ingresses along with the address to use for your dns service once you add your ingresses to dns and let dns propogate, you should be able to access different components of your opsverse stack from your browser make sure your certificate acm arn is correct in the config, otherwise your https endpoints may fail with a certificate error making updates since everything is driven by helm charts, making updates is as simple as updating the values yaml file you had created in the previous steps and re running the helm install command again charts can also be updated using helm repo update command to ensure you are always running the latest chart version make sure to look at the compatibility and deprecations in new chart versions to ensure you don't end up pushing breaking changes to your opsverse stack