Skip to content

doc updates for microsoft charts repo release #512

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ganga1980 merged 2 commits into from
Mar 22, 2021
Merged

doc updates for microsoft charts repo release #512

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8f419be
doc updates for microsoft charts repo release
ganga1980 Mar 13, 2021
6bec2f2
wip
ganga1980 Mar 22, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 35 additions & 1 deletion ReleaseProcess.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,13 +43,47 @@ This needs to be co-ordinated with Red hat and ARO-RP team for the release and

Make PR against [AKS-Engine](https://github.com/Azure/aks-engine). Refer PR https://github.com/Azure/aks-engine/pull/2318

## ARO v4, On-prem K8s, Azure Arc K8s and OpenShift v4 clusters
## ARO v4, Azure Arc K8s and OpenShift v4 clusters

Make sure azuremonitor-containers chart yamls updates with all changes going with the release and also make sure to bump the chart version, imagetag and docker provider version etc. Similar to agent container image, build pipeline automatically push the chart to container insights prod acr for canary and prod repos accordingly.
Both the agent and helm chart will be replicated to `mcr.microsoft.com`.

The way, customers will be onboard the monitoring to these clusters using onboarding scripts under `onboarding\managed` directory so please bump chart version for prod release. Once we move to Arc K8s Monitoring extension Public preview, these will be taken care so at that point of time no manual changes like this required.

## Microsoft Charts Repo release for On-prem K8s

Since HELM charts repo being deprecated, Microsoft charts repo being used for HELM chart release of on-prem K8s clusters.
To make chart release PR, fork [Microsoft-charts-repo]([https://github.com/microsoft/charts/tree/gh-pages) and make the PR against `gh-pages` branch of the upstream repo.

Refer PR - https://github.com/microsoft/charts/pull/23 for example.
Once the PR merged, latest version of HELM chart should be available in couple of mins in https://microsoft.github.io/charts/repo and https://artifacthub.io/.

Instructions to create PR
```
# 1. create helm package for the release candidate
git clone git@github.com:microsoft/Docker-Provider.git
git checkout ci_prod
cd ~/Docker-Provider/charts/azuremonitor-containers # this path based on where you have cloned the repo
helm package .

# 2. clone your fork repo and checkout gh_pages branch # gh_pages branch used as release branch
cd ~
git clone <your-forked-repo-of-microsoft-charts-repo>
cd ~/charts # assumed the root dir of the clone is charts
git checkout gh_pages

# 3. copy release candidate helm package
cd ~/charts/repo/azuremonitor-containers
# update chart version value with the version of chart being released
cp ~/Docker-Provider/charts/azuremonitor-containers/azuremonitor-containers-<chart-version>.tgz .
cd ~/charts/repo
# update repo index file
helm repo index .

# 4. Review the changes and make PR. Please note, you may need to revert unrelated changes automatically added by `helm repo index .` command

```

# 4. Monitor agent roll-out status

In Container Insights Agent (AKS) telemetry dashboard, update the agent roll status by region chart with released agent image and track rollout status. If you see any issues with agent rollout, reach out AKS on-call team for the help on investigation and understanding whats going on.