Skip to content

OCPBUGS-84834: Bump GWAPI CRDs to v1.4.1 OSSM 3.3.1 and Istio v1.28.5#1444

Open
rhamini3 wants to merge 3 commits into
openshift:release-4.21from
rhamini3:ocpbugs-84834
Open

OCPBUGS-84834: Bump GWAPI CRDs to v1.4.1 OSSM 3.3.1 and Istio v1.28.5#1444
rhamini3 wants to merge 3 commits into
openshift:release-4.21from
rhamini3:ocpbugs-84834

Conversation

@rhamini3

Copy link
Copy Markdown
Contributor

This PR is bumping OSSM and Istio to the latest z-stream version to target CVE fixes.

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 12, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels May 12, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@rhamini3: This pull request references Jira Issue OCPBUGS-84834, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This PR is bumping OSSM and Istio to the latest z-stream version to target CVE fixes.

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label May 12, 2026
@coderabbitai

coderabbitai Bot commented May 12, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: df2490ea-268d-4d9c-8492-ad3e3e89c742

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot requested review from Thealisyed and gcs278 May 12, 2026 22:35
@rhamini3

Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label May 12, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@rhamini3: This pull request references Jira Issue OCPBUGS-84834, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.z) matches configured target version for branch (4.21.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-79376 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-79376 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
  • bug has dependents

Requesting review from QA contact:
/cc @melvinjoseph86

Details

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.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label May 12, 2026
@openshift-ci openshift-ci Bot requested a review from melvinjoseph86 May 12, 2026 22:35
@rhamini3

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-gatewayapi-conformance

@melvinjoseph86

Copy link
Copy Markdown

/retest

@rhamini3

Copy link
Copy Markdown
Contributor Author

/retest-required

@melvinjoseph86

Copy link
Copy Markdown

/test e2e-vsphere-static-metallb-gatewayapi-conformance
/test e2e-baremetalds-metallb-gatewayapi-conformance

@melvinjoseph86

Copy link
Copy Markdown

Marking as verified since the bump is successful and gatewayAPI objects are created successfully

➜  oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.21.0-0-2026-05-13-143315-test-ci-ln-z1kwlkt-latest   True        False         119m    Cluster version is 4.21.0-0-2026-05-13-143315-test-ci-ln-z1kwlkt-latest
➜  oc create -f -<<EOF
apiVersion: gateway.networking.k8s.io/v1
kind: GatewayClass
metadata:
  name: openshift-default
spec:
  controllerName: openshift.io/gateway-controller/v1
EOF
gatewayclass.gateway.networking.k8s.io/openshift-default created
➜   oc get gatewayclass 
NAME                CONTROLLER                           ACCEPTED   AGE
openshift-default   openshift.io/gateway-controller/v1   True       75s
➜  oc -n openshift-operators get sub,csv,pod 
NAME                                                     PACKAGE                SOURCE             CHANNEL
subscription.operators.coreos.com/servicemeshoperator3   servicemeshoperator3   redhat-operators   stable

NAME                                                                     DISPLAY                            VERSION   REPLACES                      PHASE
clusterserviceversion.operators.coreos.com/servicemeshoperator3.v3.2.3   Red Hat OpenShift Service Mesh 3   3.2.3     servicemeshoperator3.v3.2.2   Succeeded

NAME                                         READY   STATUS    RESTARTS   AGE
pod/servicemesh-operator3-859547cc8c-lmcdh   1/1     Running   0          57s
➜  oc get istio
NAME                NAMESPACE           PROFILE   REVISIONS   READY   IN USE   ACTIVE REVISION     STATUS    VERSION   AGE
openshift-gateway   openshift-ingress             1           1       0        openshift-gateway   Healthy   v1.27.8   79s
➜  oc -n openshift-ingress get deployment
NAME                       READY   UP-TO-DATE   AVAILABLE   AGE
istiod-openshift-gateway   1/1     1            1           90s
router-default             2/2     2            2           143m
➜  oc -n openshift-ingress get gateway
NAME      CLASS               ADDRESS                                                                   PROGRAMMED   AGE
gateway   openshift-default   a48afb50837c54af0ab1807f5b8203db-1755482524.us-west-2.elb.amazonaws.com   True         13s
➜   oc get gatewayclass openshift-default -oyaml
apiVersion: gateway.networking.k8s.io/v1
kind: GatewayClass
metadata:
  creationTimestamp: "2026-05-13T17:20:25Z"
  generation: 1
  name: openshift-default
  resourceVersion: "65666"
  uid: 36a9fe54-3f8f-418c-adca-eb5477130e4c
spec:
  controllerName: openshift.io/gateway-controller/v1
status:
  conditions:
  - lastTransitionTime: "2026-05-13T17:21:10Z"
    message: Handled by Istio controller
    observedGeneration: 1
    reason: Accepted
    status: "True"
    type: Accepted


Also tested by running local conformance test and all are passing
PASS
ok  	sigs.k8s.io/gateway-api/conformance	1454.646s
apiVersion: gateway.networking.k8s.io/v1
date: "2026-05-13T23:30:53+05:30"
gatewayAPIChannel: standard
gatewayAPIVersion: v1.3.0
implementation:
  contact:
  - ""
  organization: Red Hat
  project: Openshift Service Mesh
  url: https://www.redhat.com/en/technologies/cloud-computing/openshift/container-platform
  version: 3.3.1
kind: ConformanceReport
mode: default
profiles:
- core:
    result: success
    statistics:
      Failed: 0
      Passed: 12
      Skipped: 0
  extended:
    result: success
    statistics:
      Failed: 0
      Passed: 1
      Skipped: 0
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayHTTPListenerIsolation
    - GatewayInfrastructurePropagation
    - GatewayPort8080
    unsupportedFeatures:
    - GatewayStaticAddresses
  name: GATEWAY-GRPC
  summary: Core tests succeeded. Extended tests succeeded.
- core:
    result: success
    statistics:
      Failed: 0
      Passed: 33
      Skipped: 0
  extended:
    result: success
    statistics:
      Failed: 0
      Passed: 24
      Skipped: 0
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayHTTPListenerIsolation
    - GatewayInfrastructurePropagation
    - GatewayPort8080
    - HTTPRouteBackendProtocolH2C
    - HTTPRouteBackendProtocolWebSocket
    - HTTPRouteBackendRequestHeaderModification
    - HTTPRouteBackendTimeout
    - HTTPRouteDestinationPortMatching
    - HTTPRouteHostRewrite
    - HTTPRouteMethodMatching
    - HTTPRouteParentRefPort
    - HTTPRoutePathRedirect
    - HTTPRoutePathRewrite
    - HTTPRoutePortRedirect
    - HTTPRouteQueryParamMatching
    - HTTPRouteRequestMirror
    - HTTPRouteRequestMultipleMirrors
    - HTTPRouteRequestPercentageMirror
    - HTTPRouteRequestTimeout
    - HTTPRouteResponseHeaderModification
    - HTTPRouteSchemeRedirect
    unsupportedFeatures:
    - GatewayStaticAddresses
  name: GATEWAY-HTTP
  summary: Core tests succeeded. Extended tests succeeded.
succeededProvisionalTests:
- GatewayInfrastructure
- HTTPRouteRequestPercentageMirror

/verified by @mjoseph

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label May 13, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@melvinjoseph86: This PR has been marked as verified by @mjoseph.

Details

In response to this:

Marking as verified since the bump is successful and gatewayAPI objects are created successfully

➜  oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.21.0-0-2026-05-13-143315-test-ci-ln-z1kwlkt-latest   True        False         119m    Cluster version is 4.21.0-0-2026-05-13-143315-test-ci-ln-z1kwlkt-latest
➜  oc create -f -<<EOF
apiVersion: gateway.networking.k8s.io/v1
kind: GatewayClass
metadata:
 name: openshift-default
spec:
 controllerName: openshift.io/gateway-controller/v1
EOF
gatewayclass.gateway.networking.k8s.io/openshift-default created
➜   oc get gatewayclass 
NAME                CONTROLLER                           ACCEPTED   AGE
openshift-default   openshift.io/gateway-controller/v1   True       75s
➜  oc -n openshift-operators get sub,csv,pod 
NAME                                                     PACKAGE                SOURCE             CHANNEL
subscription.operators.coreos.com/servicemeshoperator3   servicemeshoperator3   redhat-operators   stable

NAME                                                                     DISPLAY                            VERSION   REPLACES                      PHASE
clusterserviceversion.operators.coreos.com/servicemeshoperator3.v3.2.3   Red Hat OpenShift Service Mesh 3   3.2.3     servicemeshoperator3.v3.2.2   Succeeded

NAME                                         READY   STATUS    RESTARTS   AGE
pod/servicemesh-operator3-859547cc8c-lmcdh   1/1     Running   0          57s
➜  oc get istio
NAME                NAMESPACE           PROFILE   REVISIONS   READY   IN USE   ACTIVE REVISION     STATUS    VERSION   AGE
openshift-gateway   openshift-ingress             1           1       0        openshift-gateway   Healthy   v1.27.8   79s
➜  oc -n openshift-ingress get deployment
NAME                       READY   UP-TO-DATE   AVAILABLE   AGE
istiod-openshift-gateway   1/1     1            1           90s
router-default             2/2     2            2           143m
➜  oc -n openshift-ingress get gateway
NAME      CLASS               ADDRESS                                                                   PROGRAMMED   AGE
gateway   openshift-default   a48afb50837c54af0ab1807f5b8203db-1755482524.us-west-2.elb.amazonaws.com   True         13s
➜   oc get gatewayclass openshift-default -oyaml
apiVersion: gateway.networking.k8s.io/v1
kind: GatewayClass
metadata:
 creationTimestamp: "2026-05-13T17:20:25Z"
 generation: 1
 name: openshift-default
 resourceVersion: "65666"
 uid: 36a9fe54-3f8f-418c-adca-eb5477130e4c
spec:
 controllerName: openshift.io/gateway-controller/v1
status:
 conditions:
 - lastTransitionTime: "2026-05-13T17:21:10Z"
   message: Handled by Istio controller
   observedGeneration: 1
   reason: Accepted
   status: "True"
   type: Accepted


Also tested by running local conformance test and all are passing
PASS
ok  	sigs.k8s.io/gateway-api/conformance	1454.646s
apiVersion: gateway.networking.k8s.io/v1
date: "2026-05-13T23:30:53+05:30"
gatewayAPIChannel: standard
gatewayAPIVersion: v1.3.0
implementation:
 contact:
 - ""
 organization: Red Hat
 project: Openshift Service Mesh
 url: https://www.redhat.com/en/technologies/cloud-computing/openshift/container-platform
 version: 3.3.1
kind: ConformanceReport
mode: default
profiles:
- core:
   result: success
   statistics:
     Failed: 0
     Passed: 12
     Skipped: 0
 extended:
   result: success
   statistics:
     Failed: 0
     Passed: 1
     Skipped: 0
   supportedFeatures:
   - GatewayAddressEmpty
   - GatewayHTTPListenerIsolation
   - GatewayInfrastructurePropagation
   - GatewayPort8080
   unsupportedFeatures:
   - GatewayStaticAddresses
 name: GATEWAY-GRPC
 summary: Core tests succeeded. Extended tests succeeded.
- core:
   result: success
   statistics:
     Failed: 0
     Passed: 33
     Skipped: 0
 extended:
   result: success
   statistics:
     Failed: 0
     Passed: 24
     Skipped: 0
   supportedFeatures:
   - GatewayAddressEmpty
   - GatewayHTTPListenerIsolation
   - GatewayInfrastructurePropagation
   - GatewayPort8080
   - HTTPRouteBackendProtocolH2C
   - HTTPRouteBackendProtocolWebSocket
   - HTTPRouteBackendRequestHeaderModification
   - HTTPRouteBackendTimeout
   - HTTPRouteDestinationPortMatching
   - HTTPRouteHostRewrite
   - HTTPRouteMethodMatching
   - HTTPRouteParentRefPort
   - HTTPRoutePathRedirect
   - HTTPRoutePathRewrite
   - HTTPRoutePortRedirect
   - HTTPRouteQueryParamMatching
   - HTTPRouteRequestMirror
   - HTTPRouteRequestMultipleMirrors
   - HTTPRouteRequestPercentageMirror
   - HTTPRouteRequestTimeout
   - HTTPRouteResponseHeaderModification
   - HTTPRouteSchemeRedirect
   unsupportedFeatures:
   - GatewayStaticAddresses
 name: GATEWAY-HTTP
 summary: Core tests succeeded. Extended tests succeeded.
succeededProvisionalTests:
- GatewayInfrastructure
- HTTPRouteRequestPercentageMirror

/verified by @mjoseph

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.

@rhamini3

Copy link
Copy Markdown
Contributor Author

/retest-required

@rhamini3

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-ovn-hypershift-conformance

@rhamini3 rhamini3 changed the title [WIP] OCPBUGS-84834: Bump to OSSM 3.2.3 and Istio v1.27.8 OCPBUGS-84834: Bump to OSSM 3.2.3 and Istio v1.27.8 May 14, 2026
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 14, 2026
@gcs278

gcs278 commented May 15, 2026

Copy link
Copy Markdown
Contributor

I'll take a look
/assign

@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label May 25, 2026
@openshift-ci

openshift-ci Bot commented May 25, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from gcs278. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details 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

@rhamini3

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-gatewayapi-conformance

@rhamini3

Copy link
Copy Markdown
Contributor Author

/retest-required

@openshift-ci openshift-ci Bot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels May 28, 2026
Comment thread go.mod Outdated
k8s.io/utils v0.0.0-20250604170112-4c0f3b243397
sigs.k8s.io/controller-runtime v0.21.0
sigs.k8s.io/gateway-api v1.3.0
sigs.k8s.io/gateway-api v1.3.0 // The `sigs.k8s.io/gateway-api` Go module version may differ from the Gateway API CRD manifests in

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit I won't block the PR on this but if you get a chance to fix the formatting here:

Suggested change
sigs.k8s.io/gateway-api v1.3.0 // The `sigs.k8s.io/gateway-api` Go module version may differ from the Gateway API CRD manifests in
// The `sigs.k8s.io/gateway-api` Go module version may differ from the Gateway API CRD manifests in
// pkg/manifests/assets/gateway-api/. To determine which CRD version the operator installs, check
// the manifest files, not `go.mod`.
sigs.k8s.io/gateway-api v1.3.0

@rhamini3 rhamini3 force-pushed the ocpbugs-84834 branch 2 times, most recently from e103ac0 to b02087e Compare May 28, 2026 18:22
@rhamini3

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-gateway-api-conformance

@rhamini3

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-gatewayapi-conformance

@rhamini3

Copy link
Copy Markdown
Contributor Author

/test all

@rhamini3

Copy link
Copy Markdown
Contributor Author

/close

@gcs278

gcs278 commented May 28, 2026

Copy link
Copy Markdown
Contributor

/test all

@rhamini3

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-gatewayapi-conformance

@gcs278

gcs278 commented May 29, 2026

Copy link
Copy Markdown
Contributor

/testwith openshift/origin/main/e2e-gcp-ovn-upgrade openshift/origin#31232

@gcs278

gcs278 commented May 29, 2026

Copy link
Copy Markdown
Contributor

/testwith openshift/origin/main/e2e-gcp-ovn-upgrade openshift/origin#31232

@gcs278

gcs278 commented May 29, 2026

Copy link
Copy Markdown
Contributor

/testwith openshift/origin/release-4.21/e2e-gcp-ovn-upgrade openshift/origin#31232

@gcs278

gcs278 commented May 29, 2026

Copy link
Copy Markdown
Contributor

Hmm, it passed the Gateway API OLM to OLM E2E upgrade test here using my backport PR openshift/origin#31232.

In the logs I see it updated the subscription:

  Spec changes:                               
  -  StartingCSV: servicemeshoperator3.v3.2.0
  +  StartingCSV: servicemeshoperator3.v3.3.1

However, I do not see a install plan approval after this is updated - and the Istiod and gateway pods are not restarted. That's not good. I think we might have a OLM-specific upgrade bug. Let me improve my E2E test openshift/origin#31232 to check to make sure the desired Istio is installed.

Let me put a preventative hold for right now - we can remove if we confirm and fix this bug.
/hold

@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 May 29, 2026
@gcs278

gcs278 commented May 29, 2026

Copy link
Copy Markdown
Contributor

/testwith openshift/origin/release-4.21/e2e-gcp-ovn-upgrade openshift/origin#31232

@gcs278

gcs278 commented May 29, 2026

Copy link
Copy Markdown
Contributor

added a csv check just to prove that upgrades aren't working in openshift/origin#31232

@rhamini3

rhamini3 commented Jun 1, 2026

Copy link
Copy Markdown
Contributor Author

/testwith openshift/origin/release-4.21/e2e-gcp-ovn-upgrade openshift/origin#31232

@rhamini3

rhamini3 commented Jun 1, 2026

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-gatewayapi-conformance

@rhamini3

rhamini3 commented Jun 2, 2026

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-gatewayapi-conformance

@rhamini3

rhamini3 commented Jun 2, 2026

Copy link
Copy Markdown
Contributor Author

/testwith openshift/origin/release-4.21/e2e-gcp-ovn-upgrade openshift/origin#31232

@openshift-ci

openshift-ci Bot commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

@rhamini3: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-pre-release-ossm 2bfb440 link false /test e2e-aws-pre-release-ossm
ci/prow/e2e-aws-ovn 2bfb440 link true /test e2e-aws-ovn

Full PR test history. Your PR dashboard.

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants