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
Update helm chart for cilium-operator to implement per-provider opera… #11837
Conversation
Please set the appropriate release note label. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@seanmwinn please also update the release process to have the imagePullPolicy
and tag
modified.
cilium/Documentation/contributing/release/stable.rst
Lines 42 to 51 in 6d52ae4
#. Update the ``VERSION`` file to represent ``X.Y.Z+1`` | |
#. If this is the first release after creating a new release branch. Adjust the | |
image pull policy for all ``.sed`` files in ``install/kubernetes/cilium/values.yaml`` from | |
``Always`` to ``IfNotPresent``. | |
#. Update Helm chart documentation | |
#. Update ``version`` and ``appVersion`` in ``install/kubernetes/cilium/Chart.yaml`` | |
#. Update version tag in ``install/kubernetes/cilium/values.yaml`` | |
#. Update the image tag versions in the examples: |
Marked as |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall! Thanks @seanmwinn!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joestringer the release process guide needs to be updated, right?
@aanm which step changes? The makefile change I pushed expands the existing |
@joestringer step 5 https://docs.cilium.io/en/latest/contributing/release/stable/ |
@aanm oh right. Yes, we can drop steps 5 & 6 as they are achieved by step 7. That's a separate issue from this PR though, I can send a PR. |
test-me-please |
the CI seem to have failed because the proposed changes https://jenkins.cilium.io/job/Cilium-PR-K8s-newest-kernel-4.9/592/testReport/junit/Suite-k8s-1/18/K8sChaosTest_Connectivity_demo_application_Endpoint_can_still_connect_while_Cilium_is_not_running |
test-me-please |
1 similar comment
test-me-please |
Looks like the templating is wrong somewhere here, see
|
In particular, add the new operator values file to the list of files that we fix these values up for in the make target. Signed-off-by: Joe Stringer <joe@cilium.io>
Update the helm charts for for generic, aws and azure operator images. Fixes: #11800 Signed-off-by: Sean Winn <sean@isovalent.com> Signed-off-by: Joe Stringer <joe@cilium.io>
Signed-off-by: Sean Winn <sean@isovalent.com>
test-focus K8sUpdates |
Updates test is already providing some feedback: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated-Focus/259/execution/node/175/log/
Basically the Ginkgo framework is deploying v1.7-dev from helm.cilium.io using a set of Helm options defined in this branch, ie the Helm options correspond to v1.8. This discrepancy means that the |
Given these are doc changes only, we can remove the release blocker flag as we can tag the binary before this is merged. |
@tgraf my concern was more the helm changes which we would need to test in all cloud configurations prior to release. |
Sure, totally fine to re-add the release blocker label as long as we agree that we don't have to hold rc3 for it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quick status update to clarify what was merged / what is deferred to resolve in the future.
CILIUM_CHARTS := "$(ROOT_DIR)/$(RELATIVE_DIR)/cilium/" | ||
CILIUM_VALUES := "$(CILIUM_CHARTS)/values.yaml" | ||
CILIUM_CHARTS := "$(ROOT_DIR)/$(RELATIVE_DIR)/cilium" | ||
CILIUM_VALUES := "$(CILIUM_CHARTS)/values.yaml" "$(CILIUM_CHARTS)/charts/operator/values.yaml" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When rebasing, this change will still be necessary.
image: | ||
repository: operator | ||
tag: latest | ||
pullPolicy: Always | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All of the other changes were already applied in other PRs, except for this change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Well, and obviously when this changes the actual daemonset needs to take this into account)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will need to look at this closely from an upgrade instructions angle because changing the "image" value from a string to a map may cause helm to reject the upgrade.
…tor deployment for generic, aws and azure
Fixes: #11800
Signed-off-by: Sean Winn sean@isovalent.com