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

[release-4.15] CORS-3029: Add Cloud LB IPs to GCP PlatformStatus of Infrastructure CR #1705

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #1685

/assign JoelSpeed

1. Make CloudLoadBalancerConfig an union with the dnsType as a
discriminator
2. Add API, API-Int and Ingress LB IPs to Infrastructure CR's GCP
PlatformStatus
3. Add IP type
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 13, 2023

@openshift-cherrypick-robot: An error was encountered cloning bug for cherrypick for bug CORS-3029 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message. request failed. Please analyze the request body for more details. Status code: 400: {"errorMessages":["Number value expected as the Sprint id."],"errors":{"customfield_12318341":"Operation value must be a string"}}

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

In response to this:

This is an automated cherry-pick of #1685

/assign JoelSpeed

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.

Copy link
Contributor

openshift-ci bot commented Dec 13, 2023

Hello @openshift-cherrypick-robot! 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 Dec 13, 2023
@JoelSpeed
Copy link
Contributor

/hold @sadasu Can you please get the code implemented, merged, and verified for the 4.16 branch and then open placeholder backports for the changes. Once we have everything lined up, lets come back to this and get it merged, and then get the other code changes merged in quick succession

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 13, 2023
@sadasu
Copy link
Contributor

sadasu commented Dec 14, 2023

/retest-required

@sadasu
Copy link
Contributor

sadasu commented Dec 14, 2023

@JoelSpeed openshift/installer#7837 are the minimal Installer changes required to incorporate CloudLoadBalancerConfig in place of ClusterHostedDNS. And, it has merged.

openshift/installer#7838 is the 4.15 backport of the same changes.

@sadasu
Copy link
Contributor

sadasu commented Dec 14, 2023

/test e2e-azure

@JoelSpeed
Copy link
Contributor

/lgtm
/label backport-risk-assessed
/hold cancel
/override ci/prow/verify-crd-schema

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Dec 20, 2023
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 20, 2023
Copy link
Contributor

openshift-ci bot commented Dec 20, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, openshift-cherrypick-robot

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 Dec 20, 2023
Copy link
Contributor

openshift-ci bot commented Dec 20, 2023

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

In response to this:

/lgtm
/label backport-risk-assessed
/hold cancel
/override ci/prow/verify-crd-schema

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.

Copy link
Contributor

openshift-ci bot commented Dec 20, 2023

@openshift-cherrypick-robot: 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.

@yunjiang29
Copy link

/label cherry-pick-approved

Copy link
Contributor

openshift-ci bot commented Jan 4, 2024

@yunjiang29: Can not set label cherry-pick-approved: Must be member in one of these teams: [openshift-staff-engineers]

In response to this:

/label cherry-pick-approved

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.

@yunjiang29
Copy link

@jianlinliu, this PR needs your cherry-pick-approved lablel, thanks

@jianlinliu
Copy link

/label cherry-pick-approved

Copy link
Contributor

openshift-ci bot commented Jan 4, 2024

@jianlinliu: Can not set label cherry-pick-approved: Must be member in one of these teams: [openshift-staff-engineers]

In response to this:

/label cherry-pick-approved

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.

@sdodson
Copy link
Member

sdodson commented Jan 5, 2024

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jan 5, 2024
@sdodson sdodson added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jan 5, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit e4433f7 into openshift:release-4.15 Jan 5, 2024
16 checks passed
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-config-api-container-v4.15.0-202401051551.p0.ge4433f7.assembly.stream 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
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. 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