Skip to content

[release-1.28] Enable TLSv1.2 for ZTunnel when in FIPS mode (#1596)#678

Closed
zmiklank wants to merge 1 commit intoopenshift-service-mesh:release-3.2from
zmiklank:tls12_ztunnel_cherrypick
Closed

[release-1.28] Enable TLSv1.2 for ZTunnel when in FIPS mode (#1596)#678
zmiklank wants to merge 1 commit intoopenshift-service-mesh:release-3.2from
zmiklank:tls12_ztunnel_cherrypick

Conversation

@zmiklank
Copy link
Copy Markdown
Member

  • Enable TLSv1.2 for ZTunnel when in FIPS mode

This change builds on istio/ztunnel#1711 which adds TLSv1.2 support to ZTunnel when TLS12_ENABLED is set to true. This patch will always set the env var when in FIPS mode, for all versions of ZTunnel, even though it is only supported from 1.29+, but the env var will simply be ignored by versions that don't support it.

  • Make sure that FipsEnabled is restored to original value

In our tests, we sometimes set FipsEnabled manually. We should make sure to reset it to its original value during test cleanup.

…osystem#1596)

* Enable TLSv1.2 for ZTunnel when in FIPS mode

This change builds on istio/ztunnel#1711 which
adds TLSv1.2 support to ZTunnel when `TLS12_ENABLED` is set to `true`.
This patch will always set the env var when in FIPS mode, for all
versions of ZTunnel, even though it is only supported from 1.29+, but
the env var will simply be ignored by versions that don't support it.

Signed-off-by: Daniel Grimm <dgrimm@redhat.com>

* Make sure that FipsEnabled is restored to original value

In our tests, we sometimes set FipsEnabled manually. We should make sure
to reset it to its original value during test cleanup.

Signed-off-by: Daniel Grimm <dgrimm@redhat.com>

---------

Signed-off-by: Daniel Grimm <dgrimm@redhat.com>
@openshift-ci openshift-ci bot added the size/M label Feb 17, 2026
@sridhargaddam
Copy link
Copy Markdown

@zmiklank any specific reason why we are pushing this PR directly in the midstream repo and not in the sail-operator?

@zmiklank
Copy link
Copy Markdown
Member Author

@sridhargaddam Right, now I see I should have created it against upstream repo. Sorry and thanks for catching this. I will close this PR and open second one against the upstream.

@zmiklank zmiklank closed this Feb 17, 2026
@zmiklank
Copy link
Copy Markdown
Member Author

This is the new PR: istio-ecosystem#1606

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants