-
Notifications
You must be signed in to change notification settings - Fork 180
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
NE-1400: Bump to OSSM 2.5 and Gateway API v0.6.2 CRDs #1018
NE-1400: Bump to OSSM 2.5 and Gateway API v0.6.2 CRDs #1018
Conversation
@candita: This pull request references NE-1400 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:
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. |
620ab5c
to
5021078
Compare
5021078
to
d40c105
Compare
/test e2e-azure-operator |
Installation failure on an optional test |
@candita: This pull request references NE-1400 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:
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. |
d40c105
to
fdd79f8
Compare
// Istio will only create the default gateway class if this is true. | ||
"PILOT_ENABLE_GATEWAY_API_GATEWAYCLASS_CONTROLLER": "true", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the workflow from the EP, the cluster-admin creates the gatewayclass, not Istio.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can update that to say "Istio will only allow ...."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, so OSSM doesn't reconcile gatewayclasses at all without PILOT_ENABLE_GATEWAY_API_GATEWAYCLASS_CONTROLLER=true
? Is that a regression from OSSM 2.4? Then it seems like the options are (1) no Gateway API support at all or (2) cluster-admin and OSSM clash over ownership of the default gatewayclass object. Option 2 is better if we have no other option.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it is a regression from OSSM 2.4. I could ask OSSM to try to fix it in a 2.5 patch, but they don't consider this a bug. I would like to get this into the next release if possible, if only to let dev preview users play with OSSM 2.5 as-is, but it doesn't add much to the mix in terms of Gateway API.
/assign @rfredette |
- Pull the new CRD yaml from upstream and update pkg/manifests/assets/gateway-api - Update the pkg/operator/controller/gatewayclass/servicemeshcontrolplane.go to reflect changes required by OSSM 2.5.
fdd79f8
to
d9a4fe9
Compare
@candita: This pull request references NE-1400 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:
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. |
Was this an issue?
/test e2e-gcp-operator |
/test e2e-aws-operator |
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested this with our current DevPreview blog instructions: https://github.com/openshift/network-edge-tools/blob/main/docs/blogs/EnhancedDevPreviewGatewayAPI/GettingStarted.md.
And generally, everything looks good. However, the some blog instructions are now broken after this PR, for example:
- OSSM will create two new Istio deployments in the openshift-ingress namespace we don't create the default
istio-ingressgateway
deployment, so this command is incorrect now. - The automated deployment and service name changed from
demo-gateway
todemo-gateway-openshift-default
, some commands will fail - The ready condition doesn't exist, so the
Wait for the gateway deployment to be ready:
command will fail
Should we maintain our DevPreview blog instructions? Or let them go stale? Either way, I'm good with proceeding with this bump.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed a couple of these too and made some notes on them. The DevPreview instructions are specific to a release. Hopefully we make enough progress with this release that we can issue an update in OpenShift docs.
Looks good to me. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gcs278 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 |
@candita: The following test failed, say
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. |
Failures in e2e-hypershift don't seem related to this change:
Failure in e2e-aws-ovn-serial due to:
/retest-required |
a479bee
into
openshift:master
[ART PR BUILD NOTIFIER] This PR has been included in build ose-cluster-ingress-operator-container-v4.17.0-202405241212.p0.ga479bee.assembly.stream.el9 for distgit ose-cluster-ingress-operator. |
OSSM 2.5 supports Istio 1.18 and therefore only Gateway API v0.6.2 CRDS.