search

CloudHealth / helm

Apache License 2.0
8 stars 15 forks source link

[ENG-45391] Upgrade hpa endpoint #92

Closed kscherme closed 1 year ago

kscherme commented 1 year ago
  1. As part of https://cloudhealthtech.atlassian.net/browse/ENG-45391, we were going to update the HPA endpoint - however, upon investigation, we realized that an autoscaler is never needed for this application (we only ever want a customer running one collector agent pod).
  2. Change our release workflow to use the helm chart releaser (similar to https://github.com/vmware-tanzu/helm-charts). This will allow us to have release logging and a more streamlined process.
    • With this change, we will no longer need the release.sh file or index file (this will be kept in the gh-pages branch.
    • All files need to be moved to the charts directory for this to work.
vmwclabot commented 1 year ago

@kscherme, you must sign our contributor license agreement before your changes are merged. Click here to sign the agreement. If you are a VMware employee, read this for further instruction.

gm-cht commented 1 year ago

Will the tgz file location change due to this? the DNS might have to be changed by secops for this.

kscherme commented 1 year ago

Will the tgz file location change due to this? the DNS might have to be changed by secops for this.

Yes tgz file will be located at: https://github.com/CloudHealth/helm/releases/download/. Will secops need to open this route to be public?

gm-cht commented 1 year ago

Will the tgz file location change due to this? the DNS might have to be changed by secops for this.

Yes tgz file will be located at: https://github.com/CloudHealth/helm/releases/download/. Will secops need to open this route to be public?

Our instructions say helm repo add cloudhealth https://cloudhealth.github.io/helm/ .. This has to change since the chart is in a sub-folder in this path i think..

kscherme commented 1 year ago

Will the tgz file location change due to this? the DNS might have to be changed by secops for this.

Yes tgz file will be located at: https://github.com/CloudHealth/helm/releases/download/. Will secops need to open this route to be public?

Our instructions say helm repo add cloudhealth https://cloudhealth.github.io/helm/ .. This has to change since the chart is in a sub-folder in this path i think..

I tested this locally -- gh-pages still publishes the same way, so this does not need to change.