Add github workflow to push development helm charts to quay.io #25205
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michi-covalent
approved these changes
Apr 28, 2023
Signed-off-by: Chance Zibolski <chance.zibolski@gmail.com>
chancez
force-pushed
the
pr/main/chancez/push-dev-charts
branch
from
12a043b
to
a807982
Compare
|
Okay, I updated it to use a few more variables in case we want to reuse this elsewhere. CI run: https://github.com/cilium/cilium/actions/runs/4835002365/jobs/8616858840 |
|
/test Job 'Cilium-PR-K8s-1.26-kernel-net-next' failed: Click to show.Test NameFailure OutputJenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next/2054/ If it is a flake and a GitHub issue doesn't already exist to track it, comment Then please upload the Jenkins artifacts to that issue. |
|
There's nothing to test in this PR @michi-covalent |
|
i'm keeping it simple. if the button is not green, i don't merge ✅ |
|
test-1.26-net-next: hit #15455 |
|
/test-1.26-net-next |
maintainer-s-little-helper
bot
added
the
ready-to-merge
|
is the button green? yes. am i merging it? definitely. |
joestringer
added
backport-pending/1.12
backport-pending/1.13
joestringer
added
backport-done/1.13
maintainer-s-little-helper
bot
moved this from Backport pending to v1.13
to Backport done to v1.13
in 1.13.3
joestringer
added
backport-done/1.12
maintainer-s-little-helper
bot
moved this from Backport pending to v1.12
to Backport done to v1.12
in 1.12.10
joestringer
added
backport-done/1.11
This was referenced Jun 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The goal of this PR is to make it easier for developers and users to test images prior to releases being tagged. A common source of trouble is using images built in CI with the wrong version of the helm chart. This usually occurs when someone is testing an image from CI with the latest release of the chart. Typically this results in a failed install because the older chart is incompatible with the newer image.
This can simplify the testing of new changes by building a chart whenever an image is built, updating the chart to use the images built in CI. This means you can just install the chart, no need to even modify your values.yaml to use the CI images.
This was tested in a separate branch since
workflow_dispatchonly will work for workflows in the default branch. The CI ran passed here: https://github.com/cilium/cilium/actions/runs/4834815876. Normally it will only run after the image build CI workflow finishes, and or if triggered manually.Once the chart is pushed, you can use it with helm like so:
You can view the chart repo here: https://quay.io/repository/cilium-charts-dev/cilium?tab=tags