-
Notifications
You must be signed in to change notification settings - Fork 204
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
fix: add IgnoreUnexported to Node Taints comparison #1371
base: main
Are you sure you want to change the base?
Conversation
Hi @afarbos. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
✅ Deploy Preview for kubernetes-sigs-cluster-api-gcp ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
I am not clear, how to add a test in repo. Let me know if what I did is wrong. |
/ok-to-test |
Thanks @afarbos. Overall this looks good to me (just added a minor comment) and the template you modified should be enough to update the E2E test for GKE provisioning but, in this case, I see the specific GKE test cases are skipped (you can take a look at it in the prow dashboard). @cpanato @damdo @richardcase are these E2E tests skipped because there are no changes in the managed cluster code (in |
/assign @cpanato @richardcase |
2e4af5c
to
ef0b820
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: afarbos The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@afarbos: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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-sigs/prow repository. I understand the commands that are listed here. |
Hey @afarbos, thanks for this. I see the GKE tests are now running and seem to be failing, could you take a look at this? |
What type of PR is this?
/kind bug
What this PR does / why we need it:
The goal of this PR is to fix a panic after creating a cluster around node taint:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Full error and stack trace bellow:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
TODOs:
Release note: