-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
Upgrade AdmissionReview e2e test image to also support v1 #81271
Conversation
@BCLAU What do I need to do to test the agnhost image change in this PR? |
So, first of all, since this changes I don't think the image promotion automation finished yet, so someone who can build and push the image to gcr.io will have to build and push it. /cc @spiffxp |
1b6ed0b
to
d499a45
Compare
d499a45
to
0e36b6b
Compare
@BCLAU One more question: Is there a recipe for running e2e tests against a not-yet-published agnhost image. E.g steps to publish the image to my local docker repo and update e2e tests to use it? |
342b193
to
c5eb069
Compare
Nevermind, I found a way to run it locally. |
c5eb069
to
eb94ad6
Compare
/retest |
ac1c135
to
1545378
Compare
/retest |
/approve /hold |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jpbetz, liggitt 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 |
1545378
to
dbceb68
Compare
/lgtm |
/retest |
dbceb68
to
4f7543e
Compare
/retest |
e2e are passing in my development environment with new image. Steps to reproduce:
|
thanks /hold cancel |
Update webhook test image support v1beta1 and v1 AdmissionReview APIs
Arrange code so that internally, test admission handlers convert v1beta1 API requests to v1 before handling, but can easily handle versions via distinct code paths if needed in the future
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Special notes for your reviewer:
I am unfamiliar with how to test or publish the agnhost images.
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/cc @liggitt @roycaihw @sttts @caesarxuchao
/sig api-machinery
/area admission-control