Skip to content

OCPBUGS-79376: Bump to OSSM 3.3.1 and Istio v1.28.5#1406

Merged
openshift-merge-bot[bot] merged 4 commits intoopenshift:masterfrom
rhamini3:ocpbugs-79376
Apr 1, 2026
Merged

OCPBUGS-79376: Bump to OSSM 3.3.1 and Istio v1.28.5#1406
openshift-merge-bot[bot] merged 4 commits intoopenshift:masterfrom
rhamini3:ocpbugs-79376

Conversation

@rhamini3
Copy link
Copy Markdown
Contributor

This PR is bumping OSSM to v3.3.1 and Istio to v1.28.5 to include bug fixes

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 26, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

  • expected the bug to target the "4.22.0" version, but no target version was set

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 to v3.3.1 and Istio to v1.28.5 to include bug 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 Mar 26, 2026
@rhamini3
Copy link
Copy Markdown
Contributor Author

/hold

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 26, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

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 YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 3f814e15-a499-48e6-89e0-e4e47e68a657

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

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

Updated default versions for Gateway API operator and Istio: in cmd/ingress-operator/start.go the constants changed from servicemeshoperator3.v3.3.0servicemeshoperator3.v3.3.1 and v1.28.4v1.28.5. Deployment manifests (manifests/02-deployment.yaml, manifests/02-deployment-ibm-cloud-managed.yaml) set GATEWAY_API_OPERATOR_VERSION=servicemeshoperator3.v3.3.1 and ISTIO_VERSION=v1.28.5. The conformance script hack/gatewayapi-conformance.sh updates the --version argument from 3.3.0 to 3.3.1.

✨ 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 added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 26, 2026
@rhamini3
Copy link
Copy Markdown
Contributor Author

/test e2e-aws-gatewayapi-conformance

@openshift-ci openshift-ci bot requested review from gcs278 and jcmoraisjr March 26, 2026 20:25
Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@hack/gatewayapi-conformance.sh`:
- Line 65: The conformance test invocation hardcodes the OSSM version as
"--version=3.3.0"; update this flag to "--version=3.3.1" in the go test command
(the line containing go test ./conformance ... "--version=3.3.0") so the
reported/tested version matches the PR bump to OSSM 3.3.1.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 767a03e1-6fd2-4960-a141-0128bb8d6ed5

📥 Commits

Reviewing files that changed from the base of the PR and between a6176ea and 075bf7c.

📒 Files selected for processing (4)
  • cmd/ingress-operator/start.go
  • hack/gatewayapi-conformance.sh
  • manifests/02-deployment-ibm-cloud-managed.yaml
  • manifests/02-deployment.yaml

@rhamini3
Copy link
Copy Markdown
Contributor Author

/test e2e-aws-gatewayapi-conformance


SUPPORTED_FEATURES="BackendTLSPolicy,BackendTLSPolicySANValidation,GRPCRoute,Gateway,GatewayAddressEmpty,GatewayHTTPListenerIsolation,GatewayInfrastructurePropagation,GatewayPort8080,HTTPRoute,HTTPRouteBackendProtocolH2C,HTTPRouteBackendProtocolWebSocket,HTTPRouteBackendRequestHeaderModification,HTTPRouteBackendTimeout,HTTPRouteCORS,HTTPRouteDestinationPortMatching,HTTPRouteHostRewrite,HTTPRouteMethodMatching,HTTPRouteNamedRouteRule,HTTPRouteParentRefPort,HTTPRoutePathRedirect,HTTPRoutePathRewrite,HTTPRoutePortRedirect,HTTPRouteQueryParamMatching,HTTPRouteRequestMirror,HTTPRouteRequestMultipleMirrors,HTTPRouteRequestPercentageMirror,HTTPRouteRequestTimeout,HTTPRouteResponseHeaderModification,HTTPRouteSchemeRedirect,ReferenceGrant"
SKIPPED_TESTS="HTTPRouteCORSAllowCredentialsBehavior,GatewayStaticAddresses,BackendTLSPolicyConflictResolution"
SUPPORTED_FEATURES="BackendTLSPolicy,BackendTLSPolicySANValidation,GRPCRoute,Gateway,GatewayAddressEmpty,GatewayHTTPListenerIsolation,GatewayInfrastructurePropagation,GatewayPort8080,HTTPRoute,HTTPRouteBackendProtocolH2C,HTTPRouteBackendProtocolWebSocket,HTTPRouteBackendRequestHeaderModification,HTTPRouteBackendTimeout,HTTPRouteCORS,HTTPRouteDestinationPortMatching,HTTPRouteHostRewrite,HTTPRouteMethodMatching,HTTPRouteNamedRouteRule,HTTPRouteParentRefPort,HTTPRoutePathRedirect,HTTPRoutePathRewrite,HTTPRoutePortRedirect,HTTPRouteQueryParamMatching,HTTPRouteRequestMirror,HTTPRouteRequestMultipleMirrors,HTTPRouteRequestPercentageMirror,HTTPRouteRequestTimeout,HTTPRouteResponseHeaderModification,HTTPRouteSchemeRedirect,ReferenceGrant,BackendTLSPolicyConflictResolution"
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.

BackendTLSPolicyConflictResolution may still be broken, but it is worth running at least one test to see the outcome.

@candita
Copy link
Copy Markdown
Contributor

candita commented Mar 26, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 26, 2026
@gcs278
Copy link
Copy Markdown
Contributor

gcs278 commented Mar 26, 2026

@rhamini3 Be aware that this will break sail-library, unless you do the sail library 3.3.1 official "bump" here too.

If you merge before #1404, sail library will fail because no v1.28.5 helm charts exist.

If you merge after #1404, then it will find the v1.28.5 helm charts, however, due to the changes in 28cf0aa, it will pull the upstream istio image because their CSV lacks v1.28.5 istio SHAs. And upstream images don't work right now.

The best course of action for keeping noOLM working is to also do the official "bump" or vendoring of the release-3.3.1 branch that has the v1.28.5 SHAs in the CSV. That should happen pretty quickly, as it's just a backport. I'll do my best to keep tabs on the progress of the 3.3.1 CSV update, so you can vendor that here.

@gcs278
Copy link
Copy Markdown
Contributor

gcs278 commented Mar 27, 2026

The e2e-aws-operator-techpreview failures is what I was expecting per my previous comment.

@lihongan
Copy link
Copy Markdown
Contributor

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

@lihongan
Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@lihongan: This pull request references Jira Issue OCPBUGS-79376, which is invalid:

  • expected the bug to target the "4.22.0" version, but no target version was set

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.

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.

@lihongan
Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 27, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

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 openshift-ci bot requested a review from melvinjoseph86 March 27, 2026 08:15
@gcs278
Copy link
Copy Markdown
Contributor

gcs278 commented Mar 27, 2026

@rhamini3 the PR to update the SHAs is in progress: openshift-service-mesh/sail-operator#765. After that merges (and #1404 merges), we can vendor it.

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 27, 2026
@rhamini3
Copy link
Copy Markdown
Contributor Author

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

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 31, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 31, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rikatz

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

The pull request process is described 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 31, 2026
@rikatz
Copy link
Copy Markdown
Member

rikatz commented Mar 31, 2026

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 31, 2026
@rhamini3
Copy link
Copy Markdown
Contributor Author

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

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 31, 2026
@rhamini3
Copy link
Copy Markdown
Contributor Author

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


SUPPORTED_FEATURES="BackendTLSPolicy,BackendTLSPolicySANValidation,GRPCRoute,Gateway,GatewayAddressEmpty,GatewayHTTPListenerIsolation,GatewayInfrastructurePropagation,GatewayPort8080,HTTPRoute,HTTPRouteBackendProtocolH2C,HTTPRouteBackendProtocolWebSocket,HTTPRouteBackendRequestHeaderModification,HTTPRouteBackendTimeout,HTTPRouteCORS,HTTPRouteDestinationPortMatching,HTTPRouteHostRewrite,HTTPRouteMethodMatching,HTTPRouteNamedRouteRule,HTTPRouteParentRefPort,HTTPRoutePathRedirect,HTTPRoutePathRewrite,HTTPRoutePortRedirect,HTTPRouteQueryParamMatching,HTTPRouteRequestMirror,HTTPRouteRequestMultipleMirrors,HTTPRouteRequestPercentageMirror,HTTPRouteRequestTimeout,HTTPRouteResponseHeaderModification,HTTPRouteSchemeRedirect,ReferenceGrant"
SKIPPED_TESTS="HTTPRouteCORSAllowCredentialsBehavior,GatewayStaticAddresses,BackendTLSPolicyConflictResolution"
SUPPORTED_FEATURES="BackendTLSPolicy,BackendTLSPolicySANValidation,GRPCRoute,Gateway,GatewayAddressEmpty,GatewayHTTPListenerIsolation,GatewayInfrastructurePropagation,GatewayPort8080,HTTPRoute,HTTPRouteBackendProtocolH2C,HTTPRouteBackendProtocolWebSocket,HTTPRouteBackendRequestHeaderModification,HTTPRouteBackendTimeout,HTTPRouteCORS,HTTPRouteDestinationPortMatching,HTTPRouteHostRewrite,HTTPRouteMethodMatching,HTTPRouteNamedRouteRule,HTTPRouteParentRefPort,HTTPRoutePathRedirect,HTTPRoutePathRewrite,HTTPRoutePortRedirect,HTTPRouteQueryParamMatching,HTTPRouteRequestMirror,HTTPRouteRequestMultipleMirrors,HTTPRouteRequestPercentageMirror,HTTPRouteRequestTimeout,HTTPRouteResponseHeaderModification,HTTPRouteSchemeRedirect,ReferenceGrant,BackendTLSPolicyConflictResolution"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@candita @rhamini3 it will be broken because Istio folks decided they will not fix it for now: https://github.com/istio/istio/blob/ba49f7398a8542c3612788e9bd0371c079e44165/tests/integration/pilot/gateway_conformance_test.go#L67

@rhamini3 maybe add this as part of the comment, but I recommend reverting this

@rhamini3
Copy link
Copy Markdown
Contributor Author

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

@rhamini3
Copy link
Copy Markdown
Contributor Author

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

@rikatz
Copy link
Copy Markdown
Member

rikatz commented Mar 31, 2026

/lgtm

thanks

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 31, 2026
@rhamini3
Copy link
Copy Markdown
Contributor Author

/test e2e-azure-operator

@melvinjoseph86
Copy link
Copy Markdown

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

➜  oc get gatewayclass                      
NAME                CONTROLLER                           ACCEPTED   AGE
openshift-default   openshift.io/gateway-controller/v1   True       106s
➜   oc -n openshift-operators get sub,csv,pod                                                        
NAME                                                     PACKAGE                SOURCE             CHANNEL
subscription.operators.coreos.com/servicemeshoperator3   servicemeshoperator3   redhat-operators   stable

NAME                                                                     DISPLAY                            VERSION   RELEASE   REPLACES                      PHASE
clusterserviceversion.operators.coreos.com/servicemeshoperator3.v3.3.1   Red Hat OpenShift Service Mesh 3   3.3.1               servicemeshoperator3.v3.3.0   Succeeded

NAME                                         READY   STATUS    RESTARTS   AGE
pod/servicemesh-operator3-65b94c5486-gswk6   1/1     Running   0          83s

➜   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.28.5   99s

➜  oc -n openshift-ingress get gateway
NAME      CLASS               ADDRESS                                                                  PROGRAMMED   AGE
gateway   openshift-default   a98e8991c745d4301a059673d1b739c2-795465897.us-west-1.elb.amazonaws.com   True         8s
➜  oc -n openshift-ingress get svc,pod
NAME                                TYPE           CLUSTER-IP       EXTERNAL-IP                                                              PORT(S)                                 AGE
service/gateway-openshift-default   LoadBalancer   172.30.99.25     a98e8991c745d4301a059673d1b739c2-795465897.us-west-1.elb.amazonaws.com   15021:32491/TCP,80:31913/TCP            12s
service/istiod-openshift-gateway    ClusterIP      172.30.180.105   <none>                                                                   15010/TCP,15012/TCP,443/TCP,15014/TCP   2m18s
service/router-default              LoadBalancer   172.30.48.211    af7940858a6fb4d9fa61dafc8f350dd9-792344194.us-west-1.elb.amazonaws.com   80:31054/TCP,443:30681/TCP              33m
service/router-internal-default     ClusterIP      172.30.15.194    <none>       

Also tested by running local conformance test and all are passing
profiles:
- core:
    result: success
    statistics:
      Failed: 0
      Passed: 33
      Skipped: 0
  extended:
    result: partial
    skippedTests:
    - BackendTLSPolicyConflictResolution
    - HTTPRouteCORSAllowCredentialsBehavior
    statistics:
      Failed: 0
      Passed: 31
      Skipped: 2
    supportedFeatures:
    - BackendTLSPolicy
    - BackendTLSPolicySANValidation
    - GatewayAddressEmpty
    - GatewayHTTPListenerIsolation
    - GatewayInfrastructurePropagation
    - GatewayPort8080
    - HTTPRouteBackendProtocolH2C
    - HTTPRouteBackendProtocolWebSocket
    - HTTPRouteBackendRequestHeaderModification
    - HTTPRouteBackendTimeout
    - HTTPRouteCORS
    - HTTPRouteDestinationPortMatching
    - HTTPRouteHostRewrite
    - HTTPRouteMethodMatching
    - HTTPRouteNamedRouteRule
    - HTTPRouteParentRefPort
    - HTTPRoutePathRedirect
    - HTTPRoutePathRewrite
    - HTTPRoutePortRedirect
    - HTTPRouteQueryParamMatching
    - HTTPRouteRequestMirror
    - HTTPRouteRequestMultipleMirrors
    - HTTPRouteRequestPercentageMirror
    - HTTPRouteRequestTimeout
    - HTTPRouteResponseHeaderModification
    - HTTPRouteSchemeRedirect
    unsupportedFeatures:
    - GatewayStaticAddresses

/verified by @mjoseph

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 31, 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 gatewayclass                      
NAME                CONTROLLER                           ACCEPTED   AGE
openshift-default   openshift.io/gateway-controller/v1   True       106s
➜   oc -n openshift-operators get sub,csv,pod                                                        
NAME                                                     PACKAGE                SOURCE             CHANNEL
subscription.operators.coreos.com/servicemeshoperator3   servicemeshoperator3   redhat-operators   stable

NAME                                                                     DISPLAY                            VERSION   RELEASE   REPLACES                      PHASE
clusterserviceversion.operators.coreos.com/servicemeshoperator3.v3.3.1   Red Hat OpenShift Service Mesh 3   3.3.1               servicemeshoperator3.v3.3.0   Succeeded

NAME                                         READY   STATUS    RESTARTS   AGE
pod/servicemesh-operator3-65b94c5486-gswk6   1/1     Running   0          83s

➜   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.28.5   99s

➜  oc -n openshift-ingress get gateway
NAME      CLASS               ADDRESS                                                                  PROGRAMMED   AGE
gateway   openshift-default   a98e8991c745d4301a059673d1b739c2-795465897.us-west-1.elb.amazonaws.com   True         8s
➜  oc -n openshift-ingress get svc,pod
NAME                                TYPE           CLUSTER-IP       EXTERNAL-IP                                                              PORT(S)                                 AGE
service/gateway-openshift-default   LoadBalancer   172.30.99.25     a98e8991c745d4301a059673d1b739c2-795465897.us-west-1.elb.amazonaws.com   15021:32491/TCP,80:31913/TCP            12s
service/istiod-openshift-gateway    ClusterIP      172.30.180.105   <none>                                                                   15010/TCP,15012/TCP,443/TCP,15014/TCP   2m18s
service/router-default              LoadBalancer   172.30.48.211    af7940858a6fb4d9fa61dafc8f350dd9-792344194.us-west-1.elb.amazonaws.com   80:31054/TCP,443:30681/TCP              33m
service/router-internal-default     ClusterIP      172.30.15.194    <none>       

Also tested by running local conformance test and all are passing
profiles:
- core:
   result: success
   statistics:
     Failed: 0
     Passed: 33
     Skipped: 0
 extended:
   result: partial
   skippedTests:
   - BackendTLSPolicyConflictResolution
   - HTTPRouteCORSAllowCredentialsBehavior
   statistics:
     Failed: 0
     Passed: 31
     Skipped: 2
   supportedFeatures:
   - BackendTLSPolicy
   - BackendTLSPolicySANValidation
   - GatewayAddressEmpty
   - GatewayHTTPListenerIsolation
   - GatewayInfrastructurePropagation
   - GatewayPort8080
   - HTTPRouteBackendProtocolH2C
   - HTTPRouteBackendProtocolWebSocket
   - HTTPRouteBackendRequestHeaderModification
   - HTTPRouteBackendTimeout
   - HTTPRouteCORS
   - HTTPRouteDestinationPortMatching
   - HTTPRouteHostRewrite
   - HTTPRouteMethodMatching
   - HTTPRouteNamedRouteRule
   - HTTPRouteParentRefPort
   - HTTPRoutePathRedirect
   - HTTPRoutePathRewrite
   - HTTPRoutePortRedirect
   - HTTPRouteQueryParamMatching
   - HTTPRouteRequestMirror
   - HTTPRouteRequestMultipleMirrors
   - HTTPRouteRequestPercentageMirror
   - HTTPRouteRequestTimeout
   - HTTPRouteResponseHeaderModification
   - HTTPRouteSchemeRedirect
   unsupportedFeatures:
   - GatewayStaticAddresses

/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

confirmed that with NO-OLM approach istio v1.28.5 is used

status:
  conditions:
  - lastTransitionTime: "2026-03-31T19:31:54Z"
    message: Handled by Istio controller
    observedGeneration: 1
    reason: Accepted
    status: "True"
    type: Accepted
  - lastTransitionTime: "2026-03-31T20:33:33Z"
    message: istiod v1.28.5 installed
    observedGeneration: 1
    reason: Installed
    status: "True"
    type: ControllerInstalled
  - lastTransitionTime: "2026-03-31T20:33:33Z"
    message: CRDs managed by OSSM subscription via OLM
    observedGeneration: 1
    reason: ManagedByOLM
    status: "True"
    type: CRDsReady

@lihongan
Copy link
Copy Markdown
Contributor

lihongan commented Apr 1, 2026

/test e2e-aws-ovn-hypershift-conformance

@lihongan
Copy link
Copy Markdown
Contributor

lihongan commented Apr 1, 2026

/retest-required

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD df29545 and 2 for PR HEAD d1de5cb in total

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 1, 2026

@rhamini3: The following test 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-operator-techpreview d1de5cb link false /test e2e-aws-operator-techpreview

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.

@openshift-merge-bot openshift-merge-bot bot merged commit dfec6c0 into openshift:master Apr 1, 2026
21 of 22 checks passed
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@rhamini3: Jira Issue Verification Checks: Jira Issue OCPBUGS-79376
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-79376 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

This PR is bumping OSSM to v3.3.1 and Istio to v1.28.5 to include bug 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-merge-robot
Copy link
Copy Markdown
Contributor

Fix included in accepted release 4.22.0-0.nightly-2026-04-01-151631

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. 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. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants