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

SDN-4545: [Release 4-15] Add transit switch config to 4.15 #1872

Open
wants to merge 1 commit into
base: release-4.15
Choose a base branch
from

Conversation

bpickard22
Copy link
Contributor

"Backport" of #1626

The CEL validations used here are not available in 4.15 so we have to use regex to validate the fields

"Backport" of openshift#1626

The CEL validations used here are not available in 4.15 so we have to
use regex to validate the fields

Signed-off-by: Benjamin Pickard <bpickard@redhat.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 24, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 24, 2024

@bpickard22: This pull request references SDN-4545 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 story to target the "4.15.z" version, but no target version was set.

In response to this:

"Backport" of #1626

The CEL validations used here are not available in 4.15 so we have to use regex to validate the fields

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.

Copy link
Contributor

openshift-ci bot commented Apr 24, 2024

Hello @bpickard22! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

@openshift-ci openshift-ci bot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Apr 24, 2024
@bpickard22
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 24, 2024

@bpickard22: This pull request references SDN-4545 which is a valid jira issue.

In response to this:

/jira refresh

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.

Copy link
Contributor

openshift-ci bot commented Apr 24, 2024

@bpickard22: all tests passed!

Full PR test history. Your PR dashboard.

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.

@bpickard22
Copy link
Contributor Author

@JoelSpeed @trozet PTAL

@JoelSpeed
Copy link
Contributor

Validation and structure looks good now. Do we have the relevant QE testing done for the master branch feature? Are we happy that we can backport the feature without introducing any regressions in 4.15?

Have you got ack from a staff eng and your PM for the backport as well?

@knobunc
Copy link
Contributor

knobunc commented Apr 26, 2024

I grant it Staff Engineer ACK, and PM (Marc Curry) has approved this backport too.

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 26, 2024
Copy link
Contributor

openshift-ci bot commented Apr 26, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bpickard22, knobunc

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 /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 Apr 26, 2024
@bpickard22
Copy link
Contributor Author

@JoelSpeed relevant testing is done on master and I will ask qe to run regression tests once the cno pr is up

@JoelSpeed
Copy link
Contributor

@JoelSpeed relevant testing is done on master and I will ask qe to run regression tests once the cno pr is up

Can the CNO PR not go up prior to this merging? Would that not allow complete testing before we merge anything into the backported branch?

arghosh93 added a commit to arghosh93/cluster-network-operator that referenced this pull request Apr 29, 2024
This is a test commit with unmerged API changes for transit and join
switch CIDR. Ref: openshift/api#1872

Change log:
- API bump in release-4.15 branch
$ go mod edit -replace github.com/openshift/api=github.com/bpickard22/api@4.15-switch-config
$ go mod tidy
$ go mod vendor

- Made minor change to update-codegen.sh to not use controller-gen
version v0.15.0 and use v0.14.0 instead. v0.15.0 needs go version
1.22 and currently we use lower version than that.

- Ran update-codegen.sh to recreatefiles in manifests directory.

Signed-off-by: Arnab Ghosh <arnabghosh89@gmail.com>
@bpickard22
Copy link
Contributor Author

@JoelSpeed cno pr is up and i have asked qe team to run regression tests, will ping you again once that is done

@anuragthehatter
Copy link

/label qe-approved

QE regression looks good

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label May 3, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 3, 2024

@bpickard22: This pull request references SDN-4545 which is a valid jira issue.

In response to this:

"Backport" of #1626

The CEL validations used here are not available in 4.15 so we have to use regex to validate the fields

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.

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. qe-approved Signifies that QE has signed off on this PR size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants