Skip to content

components: Pin linux-bridge version#1777

Closed
ormergi wants to merge 1 commit into
kubevirt:mainfrom
ormergi:pin-linux-bridge-version
Closed

components: Pin linux-bridge version#1777
ormergi wants to merge 1 commit into
kubevirt:mainfrom
ormergi:pin-linux-bridge-version

Conversation

@ormergi

@ormergi ormergi commented Mar 28, 2024

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:
Follow-up to #1767

Use plugins latest release v1.44.1 [1] for linux-bridge component.

[1] https://github.com/containernetworking/plugins/releases/tag/v1.4.1

Special notes for your reviewer:

Release note:

NONE

Use plugins latest release v1.44.1 [1]

[1] https://github.com/containernetworking/plugins/releases/tag/v1.4.1

Signed-off-by: Or Mergi <ormergi@redhat.com>
@kubevirt-bot kubevirt-bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Mar 28, 2024
@kubevirt-bot

Copy link
Copy Markdown
Collaborator

[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 phoracek for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details 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

@ormergi

ormergi commented Mar 28, 2024

Copy link
Copy Markdown
Contributor Author

/cc @RamLavi

@kubevirt-bot kubevirt-bot requested a review from RamLavi March 28, 2024 17:07
@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@kubevirt-bot

Copy link
Copy Markdown
Collaborator

@ormergi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-cluster-network-addons-operator-unit-test f57c384 link true /test pull-cluster-network-addons-operator-unit-test
pull-e2e-cnao-kube-secondary-dns-functests f57c384 link true /test pull-e2e-cnao-kube-secondary-dns-functests
pull-e2e-cluster-network-addons-operator-macvtap-cni-functests f57c384 link true /test pull-e2e-cluster-network-addons-operator-macvtap-cni-functests
pull-e2e-cluster-network-addons-operator-br-marker-functests f57c384 link true /test pull-e2e-cluster-network-addons-operator-br-marker-functests
pull-e2e-cluster-network-addons-operator-ovs-cni-functests f57c384 link true /test pull-e2e-cluster-network-addons-operator-ovs-cni-functests
pull-e2e-cluster-network-addons-operator-kubemacpool-functests f57c384 link true /test pull-e2e-cluster-network-addons-operator-kubemacpool-functests
pull-e2e-cluster-network-addons-operator-multus-functests f57c384 link true /test pull-e2e-cluster-network-addons-operator-multus-functests
pull-e2e-cnao-multus-dynamic-networks-functests f57c384 link true /test pull-e2e-cnao-multus-dynamic-networks-functests
pull-e2e-cluster-network-addons-operator-workflow-k8s f57c384 link true /test pull-e2e-cluster-network-addons-operator-workflow-k8s
pull-e2e-cluster-network-addons-operator-monitoring-k8s f57c384 link true /test pull-e2e-cluster-network-addons-operator-monitoring-k8s
pull-e2e-cluster-network-addons-operator-lifecycle-k8s f57c384 link true /test pull-e2e-cluster-network-addons-operator-lifecycle-k8s
Details

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. I understand the commands that are listed here.

channels:
- name: alpha
currentCSV: cluster-network-addons-operator.0.90.1
currentCSV: cluster-network-addons-operator.99.0.0

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

i dont think it is related to the PR ?

Comment thread cluster/operator-push.sh
Comment on lines -24 to +25
manifest_registry=$DEV_IMAGE_REGISTRY
push_registry=$manifest_registry
manifest_registry=$DEV_MANIFEST_REGISTRY
push_registry=$DEV_IMAGE_REGISTRY

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

it also not related to the PR scope
even if we need to fix stuff about those vars, lets do it on a separate PR please and all the way ?

this does work atm fwiw

export KUBEVIRT_PROVIDER=external
export DEV_IMAGE_REGISTRY=quay.io/oshoval

users:
- system:serviceaccount:kube-system:passt-binding-cni
volumes:
- "*" No newline at end of file

@oshoval oshoval Apr 1, 2024

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

missing new line

I think we need please to wrap with SCC enabled, as we have on data/linux-bridge/001-rbac.yaml
(also the SA user as done on DS)
i think we should move this also to 001-rbac please, it is better practice it is created before the DS
(anyhow we are eventually consistent), and all the SA / SCC are there already

@kubevirt-bot

Copy link
Copy Markdown
Collaborator

PR needs rebase.

Details

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 added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 16, 2024
@RamLavi

RamLavi commented Apr 30, 2024

Copy link
Copy Markdown
Collaborator

@ormergi what's the status on this PR?

@RamLavi

RamLavi commented May 2, 2024

Copy link
Copy Markdown
Collaborator

@ormergi I'm closing this PR. If you need it again, feel free to reopen :)

@RamLavi RamLavi closed this May 2, 2024
@ormergi

ormergi commented May 2, 2024

Copy link
Copy Markdown
Contributor Author

Sorry for late response, I still think it worth working on it I will post new PR as soon as I have capacity 🙂

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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. release-note-none Denotes a PR that doesn't merit a release note. size/M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants