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-4600: Add NetworkDiagnosticsConfig to the default featureset #1886

Merged
merged 1 commit into from
May 15, 2024

Conversation

kyrtapz
Copy link
Contributor

@kyrtapz kyrtapz commented May 10, 2024

@openshift-ci-robot
Copy link

openshift-ci-robot commented May 10, 2024

@kyrtapz: This pull request references SDN-4600 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.16.0" version, but no target version was set.

In response to this:

Enhancement: openshift/enhancements#1585
E2E tests: openshift/origin#28719

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 May 10, 2024
@kyrtapz
Copy link
Contributor Author

kyrtapz commented May 10, 2024

/cc @huiran0826

Copy link
Contributor

openshift-ci bot commented May 10, 2024

Hello @kyrtapz! 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 requested a review from huiran0826 May 10, 2024 08:09
@openshift-ci openshift-ci bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label May 10, 2024
@openshift-ci openshift-ci bot requested review from knobunc and sjenning May 10, 2024 08:09
@kyrtapz
Copy link
Contributor Author

kyrtapz commented May 10, 2024

/test e2e-aws-serial

@kyrtapz
Copy link
Contributor Author

kyrtapz commented May 13, 2024

/test e2e-aws-serial
/test e2e-aws-serial-techpreview

@huiran0826
Copy link

LGTM

@huiran0826
Copy link

/label qe-approved

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

openshift-ci-robot commented May 13, 2024

@kyrtapz: This pull request references SDN-4600 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.16.0" version, but no target version was set.

In response to this:

Enhancement: openshift/enhancements#1585
E2E tests: openshift/origin#28719

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.

@kyrtapz
Copy link
Contributor Author

kyrtapz commented May 13, 2024

/test e2e-aws-serial-techpreview

@kyrtapz
Copy link
Contributor Author

kyrtapz commented May 13, 2024

/retest

Copy link
Contributor

@trozet trozet left a comment

Choose a reason for hiding this comment

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

/lgtm

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

Looking at the verify-schema, we should probably update the list tags that are missing

error in config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_networks.crd.yaml: ListsMustHaveSSATags: crd/networks.config.openshift.io version/v1 field/^.status.serviceNetwork must set x-kubernetes-list-type
		error in config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_networks.crd.yaml: ListsMustHaveSSATags: crd/networks.config.openshift.io version/v1 field/^.status.clusterNetwork must set x-kubernetes-list-type

I would assume both of these can just be set to atomic since the only actor on status fields should be the operator right?

// +listType=atomic

Otherwise as far as I can tell this looks good to go, you have tests (which look green, you have QE sign off, all generation appears to be up to date

@kyrtapz
Copy link
Contributor Author

kyrtapz commented May 14, 2024

Looking at the verify-schema, we should probably update the list tags that are missing

error in config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_networks.crd.yaml: ListsMustHaveSSATags: crd/networks.config.openshift.io version/v1 field/^.status.serviceNetwork must set x-kubernetes-list-type
		error in config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_networks.crd.yaml: ListsMustHaveSSATags: crd/networks.config.openshift.io version/v1 field/^.status.clusterNetwork must set x-kubernetes-list-type

I would assume both of these can just be set to atomic since the only actor on status fields should be the operator right?

// +listType=atomic

Sounds good, I can look into it. Since this is an unrelated change I would like to keep it separate from this PR.

@JoelSpeed
Copy link
Contributor

/lgtm
/override ci/prow/verify-crd-schema
/override ci/prow/verify

We have a follow up to fix the SSA tags, and the verify is complaining of missing E2E but we have that linked here and QE approval

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 15, 2024
Copy link
Contributor

openshift-ci bot commented May 15, 2024

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify, ci/prow/verify-crd-schema

In response to this:

/lgtm
/override ci/prow/verify-crd-schema
/override ci/prow/verify

We have a follow up to fix the SSA tags, and the verify is complaining of missing E2E but we have that linked here and QE approval

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.

@kyrtapz
Copy link
Contributor Author

kyrtapz commented May 15, 2024

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label May 15, 2024
Signed-off-by: Patryk Diak <pdiak@redhat.com>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label May 15, 2024
@kyrtapz
Copy link
Contributor Author

kyrtapz commented May 15, 2024

Had to rebase to resolve conflicts in the auto-generated files.
@JoelSpeed ptal

@JoelSpeed
Copy link
Contributor

/lgtm

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

openshift-ci bot commented May 15, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, kyrtapz, trozet

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-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 14ae5de and 2 for PR HEAD 0385715 in total

@JoelSpeed
Copy link
Contributor

/override ci/prow/verify-crd-schema
/override ci/prow/verify

Copy link
Contributor

openshift-ci bot commented May 15, 2024

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify, ci/prow/verify-crd-schema

In response to this:

/override ci/prow/verify-crd-schema
/override ci/prow/verify

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.

Copy link
Contributor

openshift-ci bot commented May 15, 2024

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

@openshift-merge-bot openshift-merge-bot bot merged commit 0f9dbca into openshift:master May 15, 2024
18 checks passed
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-config-api-container-v4.17.0-202405151441.p0.g0f9dbca.assembly.stream.el9 for distgit ose-cluster-config-api.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. 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/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants