Closed EmilienM closed 1 month ago
@EmilienM: This pull request references RFE-6242 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 feature request to target the "4.18.0" version, but no target version was set.
Hello @EmilienM! 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.
/hold cc @Miciah for information. Feel free to tag your team. @mdbooth let me know if we want to make it explicit that it's for external scope LBs
CPO makes it explicit that it's for external LB:
/test verify-crd-schema
/assign
I need to run something like: /override verify-crd-schema
Because we are violating API validations since this change is not backward compatible. cc @JoelSpeed for review on that one.
@EmilienM: EmilienM unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers.
@EmilienM Is this the one that literally just merged?
Now that it's merged, renaming it means you have to create a tombstone, a marker that shows for ever what the field name was and what its type was, so that we never re-use it.
Out of interest, why is floatingIP a better name?
@EmilienM Is this the one that literally just merged?
Yes... :'(
Now that it's merged, renaming it means you have to create a tombstone, a marker that shows for ever what the field name was and what its type was, so that we never re-use it.
ok
Out of interest, why is floatingIP a better name?
Discussion: https://redhat-internal.slack.com/archives/CH98TDJUD/p1727796033056959
/approve /assign @Miciah
/override ci/prow/verify-crd-schema
Removing a field that is in a tech preview struct and never really saw the light of day, field is tombstoned to prevent us from re-introducing as a different serialisation in the future
@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify-crd-schema
/approve cancel
Some back and forth still happening about this it seems
/hold cancel
@EmilienM: This pull request references RFE-6242 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 feature request to target the "4.18.0" version, but no target version was set.
@Miciah thanks for the quick review. I think I addressed everything.
Thanks! /lgtm
verify-crd-schema is failing with a bunch of loadBalancerIP may not be removed
errors. I don't know if that's something @JoelSpeed would override since we have the tombstone, or whether something needs to be changed in the PR itself.
Oh, sorry, I see https://github.com/openshift/api/pull/2051#issuecomment-2390968240 now. We just need the same /override
again since you pushed changes.
/override ci/prow/verify-crd-schema /lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: EmilienM, JoelSpeed, Miciah
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify-crd-schema
@EmilienM: all tests passed!
Full PR test history. Your PR dashboard.
[ART PR BUILD NOTIFIER]
Distgit: ose-cluster-config-api This PR has been included in build ose-cluster-config-api-container-v4.18.0-202410041311.p0.gb1f700b.assembly.stream.el9. All builds following this will include this PR.
This was poorly named and this hasn't been used anywhere so we can make the change while it's still time.
Also add CEL validation to make sure the field is only used for external LB (and add tests).