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
Add a kubectl rollout undo e2e test #119915
Conversation
Please note that we're already in Test Freeze for the Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Sat Aug 12 10:37:24 UTC 2023. |
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
9f0eaf6
to
2c55f16
Compare
/cc @atiratree |
thx for the update |
/hold cancel Thanks |
@aojea Updated, PTAL |
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.
A few minor nits, pls ping me when you get them updated.
test/e2e/kubectl/rollout.go
Outdated
}) | ||
|
||
ginkgo.Describe("undo", func() { | ||
deploymentYaml := commonutils.SubstituteImageName(string(readTestFileOrDie(labeledDeploymentFilename))) |
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.
I still don't understand why you can't use the existing files, rather than creating yet another one?
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 want to test that the deployment has only the original set of labels and annotations? To confirm this, it might be good to add some to the original yaml. And I'm not sure whether changing the existing files will break sth, so I created a new one. If it's ok I can add some labels to the existing file and then use 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.
kindly ping @soltysh :)
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.
Right, but you only inject new envs, thus re-using all the labels and annotations just to ensure they don't change after rollback, so what's stopping you from using an existing deployment file?
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, it's not that complicated. I'm just not sure if it's ok to modify an existing file. Updated to use httpd yaml
now. I'll squash if the rest is ok.
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.
ping @soltysh
ping @soltysh |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: AxeZhan, dims, pacoxu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
LGTM label has been added. Git tree hash: 7c5313f9ceee271159240e6e76cedc04bd7d6cd1
|
/retest |
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/119915/pull-kubernetes-e2e-gce/1711034185398882304 failed for a recent top flake #121013 that was fixed early today. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Currently we don't have test for
kubectl rollout undo
,some code changes may affect this behavior(take #116759 as an example). We should add some tests to always ensurekubectl rollout undo
is not broken. This pr adds a simple e2e test for it.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: