Skip to content

feat: use centralized TLS configuration from knative/pkg/tls#8901

Open
Fedosin wants to merge 1 commit intoknative:mainfrom
Fedosin:eventing-tls
Open

feat: use centralized TLS configuration from knative/pkg/tls#8901
Fedosin wants to merge 1 commit intoknative:mainfrom
Fedosin:eventing-tls

Conversation

@Fedosin
Copy link

@Fedosin Fedosin commented Mar 6, 2026

Fixes #

Proposed Changes

Bump knative.dev/pkg to pick up the new knative.dev/pkg/tls package and replace the hardcoded TLS server config in eventingtls with the shared DefaultConfigFromEnv utility. This enables environment-based control of MinVersion, MaxVersion, CipherSuites, and CurvePreferences for all eventing TLS servers (broker filter/ingress, IMC dispatcher, job sink, auth proxy, request-reply).
Since DefaultConfigFromEnv defaults to TLS 1.3 but eventing historically defaults to TLS 1.2, GetTLSServerConfig falls back to 1.2 unless TLS_MIN_VERSION is explicitly set.
Also wires up TLS for the RequestReply data plane, which previously had a TODO placeholder.

Pre-review Checklist

  • At least 80% unit test coverage
  • E2E tests for any new behavior
  • Docs PR for any user-facing impact
  • Spec PR for any new API feature
  • Conformance test for any change to the spec

Release Note

All eventing TLS servers now support configurable TLS settings (min/max version, cipher suites, curve preferences) via environment variables TLS_MIN_VERSION, TLS_MAX_VERSION, TLS_CIPHER_SUITES, and TLS_CURVE_PREFERENCES. The webhook reads WEBHOOK_TLS_* variants automatically. The default minimum TLS version remains 1.2.

Docs

@knative-prow
Copy link

knative-prow bot commented Mar 6, 2026

There are empty aliases in OWNER_ALIASES, cleanup is advised.

@knative-prow knative-prow bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Mar 6, 2026
@knative-prow knative-prow bot requested review from Cali0707 and pierDipi March 6, 2026 11:48
@codecov
Copy link

codecov bot commented Mar 6, 2026

Codecov Report

❌ Patch coverage is 73.68421% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 50.72%. Comparing base (3acf87a) to head (66d3915).
⚠️ Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
cmd/requestreply/main.go 58.33% 5 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8901      +/-   ##
==========================================
+ Coverage   50.67%   50.72%   +0.04%     
==========================================
  Files         409      409              
  Lines       21694    21708      +14     
==========================================
+ Hits        10994    11011      +17     
+ Misses       9848     9845       -3     
  Partials      852      852              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Fedosin
Copy link
Author

Fedosin commented Mar 6, 2026

/hold

blocked by #8900

@knative-prow knative-prow bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 6, 2026
@knative-prow knative-prow bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Mar 6, 2026
Bump knative.dev/pkg to pick up the new knative.dev/pkg/tls package
and replace the hardcoded TLS server config in eventingtls with
the shared DefaultConfigFromEnv utility. This enables environment-based
control of MinVersion, MaxVersion, CipherSuites, and CurvePreferences
for all eventing TLS servers (broker filter/ingress, IMC dispatcher,
job sink, auth proxy, request-reply).
Since DefaultConfigFromEnv defaults to TLS 1.3 but eventing historically
defaults to TLS 1.2, GetTLSServerConfig falls back to 1.2 unless
TLS_MIN_VERSION is explicitly set.
Also wires up TLS for the RequestReply data plane, which previously had
a TODO placeholder.

Signed-off-by: Mikhail Fedosin <mfedosin@redhat.com>
@Fedosin
Copy link
Author

Fedosin commented Mar 6, 2026

/hold cancel

@knative-prow knative-prow bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 6, 2026
Copy link
Contributor

@twoGiants twoGiants left a comment

Choose a reason for hiding this comment

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

/approve
/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Mar 6, 2026
@knative-prow
Copy link

knative-prow bot commented Mar 6, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Fedosin, twoGiants
Once this PR has been reviewed and has the lgtm label, please assign aliok for approval. 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

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

Labels

lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants