Esri / arcgis-gitops

GitHub Actions workflows for ArcGIS Enterprise deployment and operation
Apache License 2.0
6 stars 1 forks source link

Streamline enterprise-k8s-organization updates and upgrades #55

Closed pbobov closed 6 months ago

pbobov commented 6 months ago

ArcGIS Enterprise on Kubernetes updates and upgrades are supported by enterprise-k8s-organization workflow, but it the UX needs improvements.

Generate Upgrade Tokens

Updates and upgrades of "Helm Charts for ArcGIS Enterprise on Kubernetes" releases require providing an upgrade token.

"An ArcGIS token generated through the https://enterpriseFQDN/context/sharing/rest/generateToken endpoint. This token is used for upgrades and it needs to be a long lived token of at least 6 hours or more and created using an ArcGIS Enterprise organization administrator account."

The current implementation of enterprise-k8s-organization workflow retrieves the upgrade token from the config file along with other helm chart's values.

To streamline the workflow, arcgis-enterprise-k8s/organization Terraform module should generate the upgrade token using enterprise-admin-cli and supply it to the Helm chart's values.

Track Upgrade Status

The current implementation of enterprise-k8s-organization workflow retrieves the Helm install log from "arcgis-pre-install-hook-job" pod's log. But updates of the Helm release use different pod - "arcgis-pre-upgrade-hook-job". The workflow does not retrieve logs from this pod.

To streamline the workflow, arcgis-enterprise-k8s/organization Terraform module should retrieve the Helm release update logs.