feat(istio): add option to use post-quantum key exchange#2752
Open
lemmarathon wants to merge 1 commit into
Open
feat(istio): add option to use post-quantum key exchange#2752lemmarathon wants to merge 1 commit into
lemmarathon wants to merge 1 commit into
Conversation
Add an opt-in, default-off knob that forces post-quantum hybrid key exchange (X25519MLKEM768) across the Istio mesh by setting COMPLIANCE_POLICY=pqc on istiod and ztunnel. Supported only on the non-FIPS upstream flavor. - src/istio/common/zarf.yaml: shared ISTIO_COMPLIANCE_POLICY chart variable on the istiod (pilot.env.COMPLIANCE_POLICY) and ztunnel (env.COMPLIANCE_POLICY) charts, no default so the unset case renders identically to main - bundles/k3d-standard and k3d-slim-dev: expose the variable as a bundle override on both charts and document it in each bundle README - docs: new reference page and networking how-to (accepted value pqc, default-off, ambient + upstream-only support matrix, force-everywhere caveats) - test/vitest/istio-pqc.spec.ts: PQC force-mode scenario (gated by PQC_TESTS) asserting the negotiated group, classical-client rejection, and COMPLIANCE_POLICY=pqc on both workloads - tasks and .github/workflows/test-pqc.yaml: deploy/test wiring for the separate upstream PQC scenario Validated on k3d: the default-off suite is green (120 vitest + 15 playwright, 0 failed; no COMPLIANCE_POLICY env on either workload) and the PQC scenario is green (3/3 assertions; the tenant gateway negotiates X25519MLKEM768 and rejects classical-only clients). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
lemmarathon
changed the title
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
1 participant
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.
Description
Add an opt-in, default-off knob that forces post-quantum hybrid key exchange (X25519MLKEM768) across the Istio mesh by setting COMPLIANCE_POLICY=pqc on istiod and ztunnel. Supported only on the non-FIPS upstream flavor.
Validated on k3d: the default-off suite is green (120 vitest + 15 playwright, 0 failed; no COMPLIANCE_POLICY env on either workload) and the PQC scenario is green (3/3 assertions; the tenant gateway negotiates X25519MLKEM768 and rejects classical-only clients).
Type of change
Steps to Validate
istio-pqc.spec.tsChecklist before merging