[release-3.1] Automator: Update Istio module#669
Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift-service-mesh:release-3.1from Mar 4, 2026
Conversation
|
/retest |
1 similar comment
Collaborator
|
/retest |
Collaborator
|
Cherry pick are merged in the branch, the changes should be working now |
fjglira
approved these changes
Feb 16, 2026
openshift-service-mesh-bot
force-pushed
the
release-1.26-release-3.1-bump-istio-mod-1.26-b9f31a77
branch
from
8c0e3b3 to
aaeae9b
Compare
|
/retest |
openshift-service-mesh-bot
force-pushed
the
release-1.26-release-3.1-bump-istio-mod-1.26-b9f31a77
branch
2 times, most recently
from
d554432 to
2d36a08
Compare
|
/retest |
openshift-service-mesh-bot
force-pushed
the
release-1.26-release-3.1-bump-istio-mod-1.26-b9f31a77
branch
from
2d36a08 to
0c35f41
Compare
|
/retest |
1 similar comment
|
/retest |
openshift-merge-bot
bot
merged commit 988ac00
into
openshift-service-mesh:release-3.1
8 checks passed
|
@openshift-service-mesh-bot: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
dcillera
pushed a commit
to dcillera/sail-operator
that referenced
this pull request
Mar 19, 2026
…e-mesh#667) (openshift-service-mesh#669) (openshift-service-mesh#254) We use `-ldflags` to set the `istioversion.versionsFilename` variable, but this only works when building the binary. It doesn't work when running ginkgo-based e2e tests. When the `versionsFilename` is not set via ldflags, it will now use the environment variable `VERSIONS_YAML_FILE`. If this env var isn't set, we default to `versions.yaml`. (cherry picked from commit 148eb64) Signed-off-by: Marko Lukša <mluksa@redhat.com>
dcillera
pushed a commit
to dcillera/sail-operator
that referenced
this pull request
Mar 19, 2026
…e-mesh#667) (openshift-service-mesh#669) We use `-ldflags` to set the `istioversion.versionsFilename` variable, but this only works when building the binary. It doesn't work when running ginkgo-based e2e tests. When the `versionsFilename` is not set via ldflags, it will now use the environment variable `VERSIONS_YAML_FILE`. If this env var isn't set, we default to `versions.yaml`. (cherry picked from commit 148eb64) Signed-off-by: Marko Lukša <mluksa@redhat.com>
dcillera
pushed a commit
to dcillera/sail-operator
that referenced
this pull request
Mar 19, 2026
* upstream/release-1.0: Make environment variable consistent (openshift-service-mesh#664) Add multi control plane e2e tests (openshift-service-mesh#610) (openshift-service-mesh#670) Ensure e2e tests use the correct versions yaml file (openshift-service-mesh#667) (openshift-service-mesh#669) Add version alias support (openshift-service-mesh#566) (openshift-service-mesh#662) Add missing link for: Example using the RevisionBased strategy and an IstioRevisionTag # Conflicts: # bundle/manifests/sailoperator.clusterserviceversion.yaml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Generated by Automator - 2026-03-04T05:30:05+00:00