-
Notifications
You must be signed in to change notification settings - Fork 2.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
Migrate Network Policy testjob to podutils #20336
Migrate Network Policy testjob to podutils #20336
Conversation
/assign @aojea @jayunit100 |
e096631
to
2bafe83
Compare
Looks ok to me ! Should we merge and iterate on this ? I don’t see any logic changes so as long as it’s plugged in to the new stuff properly we’re good !!!!! |
The biggest change here is that we don't rely on bootstrap.py anymore to create the resources, pull artifacts, etc etc. It's not a huge change, but sig-testing has deprecated bootstrap.py and asked to migrate some jobs, so I guess this is a good start :) |
extra_refs: | ||
- org: kubernetes | ||
repo: test-infra | ||
base_ref: master | ||
path_alias: k8s.io/test-infra |
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.
why do you need to pull k8s.io/test-infra?
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.
Because of /workspace/scenarios/kubernetes_e2e.py
which is in test-infra repo :)
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.
Wait, I'm trying to remember why actually we used this, and maybe wasn't because of the scenarios, but because of 67e14ce#diff-9495ba672589316a9265fd090ecb9c3c74fd414a11386acafda27df4bd409409
As we do not use anything at test-infra I'll remove 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.
Also, I'm wondering if --stage=gs://kubernetes-release-pull/ci/pull-kubernetes-e2e-ubuntu-gce-network-policies is necessary or if this is also covered by podutils, BUT I think for now will leave this way
2bafe83
to
851679b
Compare
Removed the extra-args, left the stage=gs:// because I guess podutils only deals with the artifacts pushing, not the staging :) |
let´s tackle this next week, the jobs look stable but we should let them soak |
Signed-off-by: Ricardo Pchevuzinske Katz <ricardo.katz@gmail.com>
851679b
to
270eaf8
Compare
/test pull-test-infra-integration |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea, rikatz 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 |
@rikatz: Updated the
In response to this:
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. |
Signed-off-by: Ricardo Pchevuzinske Katz ricardo.katz@gmail.com
Started migrating sig-net jobs to podutils, for now let's see if the network policy job works fine :)
Part of: #20324