Skip to content

Conversation

@galkremer1
Copy link
Member

Jira: https://issues.redhat.com/browse/CNV-62004

  • Removing the default bridging interface
  • Change the "Add another interfaceType interface" label to "Add interfaceType interface" when no interfaces are currently present (see demo below).

Demo:

Screen.Recording.2025-09-10.at.12.39.14.PM.mov

@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 10, 2025

@galkremer1: This pull request references CNV-62004 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.21.0" version, but no target version was set.

Details

In response to this:

Jira: https://issues.redhat.com/browse/CNV-62004

  • Removing the default bridging interface
  • Change the "Add another interfaceType interface" label to "Add interfaceType interface" when no interfaces are currently present (see demo below).

Demo:

Screen.Recording.2025-09-10.at.12.39.14.PM.mov

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 10, 2025
@openshift-ci openshift-ci bot requested review from upalatucci and yaacov September 10, 2025 16:41
name: 'policy-name',
},
spec: {
desiredState: {
Copy link
Member Author

Choose a reason for hiding this comment

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

Removed default interface

Comment on lines +87 to +89
{t(`Add ${noCurrentStepInterfaces ? '' : 'another '}{{label}} interface`, {
label: label.toLowerCase(),
})}

Choose a reason for hiding this comment

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

this will not be translated correctly. You should have two distinct translations here.

Copy link
Member Author

Choose a reason for hiding this comment

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

I added another translation. Did I miss anything?

@upalatucci
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 11, 2025
@upalatucci
Copy link

/approve

@openshift-ci
Copy link

openshift-ci bot commented Sep 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: galkremer1, upalatucci

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

The pull request process is described 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 12, 2025
@galkremer1
Copy link
Member Author

/retest

@openshift-ci
Copy link

openshift-ci bot commented Sep 12, 2025

@galkremer1: all tests passed!

Full PR test history. Your PR dashboard.

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

@openshift-merge-bot openshift-merge-bot bot merged commit de74d7e into openshift:main Sep 12, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants