-
Notifications
You must be signed in to change notification settings - Fork 21
[CLOUDP-350669] Publish helm chart to OCI registry for dev/staging workflows #507
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.
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
base: master
Are you sure you want to change the base?
Conversation
MCK 1.6.0 Release NotesNew Features
Bug Fixes
|
5f0938b
to
1b61956
Compare
e885549
to
92d2fe6
Compare
1. Move file from scripts to scripts/relese 2. call python files from .sh files so that we can use build_scenario env var
Hi @MaciejKaras, |
@anandsyncs can you please have a look as well? |
@viveksinghggits It would also be great if you can mention in the PR description what exactly is the issue that prevents us from calling |
I can do that. |
Summary
In an effort to start using OCI compatible container registries as our helm chart repos, this PR makes the change package and publish our helm chart to ECR registry. A new task
publish_helm_chart
is introduced in the build variantinit_test_run
which packages and publishes the chart.The details about the versioning of the chart can be found in the document here.
There were two wrappers (shell scripts) introduced as part of this and the reason was we wanted to call the python scripts (
helm_registry_login.py
andpublish_helm_chart.py
) from.evergreen-function.yaml
passing an argument that's build scenario. Build scenario is already set as env var in the evg host, but there isn't a way to do this, in other words, we couldn't do below from the.evergreen-functions.yaml
fileAnd because of that we had to write the wrapper that would call the python script with correct argument after reading the env var.
Proof of Work
patch and staging evg runs. Notice at the end of the log that dev workflow is pushing to diff repository and staging to different.
Successful run of
init_test_run
variant in this PR would also work.Checklist
skip-changelog
label if not needed