Skip to content
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

Explicitly set REGISTRY env in ovs-cni jobs #3356

Closed
wants to merge 1 commit into from

Conversation

ykulazhenkov
Copy link

@ykulazhenkov ykulazhenkov commented Apr 19, 2024

What this PR does / why we need it:

Explicitly set REGISTRY env in ovs-cni jobs
This change is required because default registry in the Makefile in the ovs-cni repo was changed to ghcr.io/k8snetworkplumbingwg.

Special notes for your reviewer:

Context: k8snetworkplumbingwg/ovs-cni#307
Example of a failed job https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/logs/main-ovs-cni/1781239529819082752

NONE

@phoracek Do we want to continue push to quay in addition to GH registry? If yes, then I believe that this patch will fix the push jobs.

This change is required because default registry in the Makefile in
the ovs-cni repo was to ghcr.io/k8snetworkplumbingwg.

Signed-off-by: Yury Kulazhenkov <[email protected]>
@kubevirt-bot kubevirt-bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Apr 19, 2024
@kubevirt-bot
Copy link
Contributor

Hi @ykulazhenkov. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

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/test-infra repository.

@kubevirt-bot kubevirt-bot requested review from EdDev and phoracek April 19, 2024 10:55
@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign alonakaplan for approval. For more information see the Kubernetes Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

- "-c"
- "cat $QUAY_PASSWORD | docker login --username $(cat $QUAY_USER) --password-stdin=true quay.io && make docker-build docker-push"
- "-ce"
- |
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cmd format is aligned with "release-ovs-cni" job

@phoracek
Copy link
Member

@ykulazhenkov I don't think there is a reason to keep pushing to the old registry. It would be probably better to remove this automation, so we have less stuff to maintain.

@ykulazhenkov
Copy link
Author

ykulazhenkov commented Apr 19, 2024

@ykulazhenkov I don't think there is a reason to keep pushing to the old registry. It would be probably better to remove this automation, so we have less stuff to maintain.

Okay, thanks. Then, I will close this PR. I don't know the exact list of jobs that are no longer needed. Can you submit a PR to remove them? Thanks

@phoracek
Copy link
Member

@ykulazhenkov sure, fair enough, posted: #3357

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants