Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addition of TLSRoute with Terminate mode conformance tests #3466

Open
Tracked by #3165
mlavacca opened this issue Nov 21, 2024 · 3 comments
Open
Tracked by #3165

Addition of TLSRoute with Terminate mode conformance tests #3466

mlavacca opened this issue Nov 21, 2024 · 3 comments
Assignees
Labels
area/conformance-test Issues or PRs related to Conformance tests.

Comments

@mlavacca
Copy link
Member

What would you like to be added:

Conformance tests for TLSRoutes with TLS terminate mode.

Why this is needed:

GEP-2907 update listed the TLS modes supported by each protocol. Since we need to support both Passthrough and Terminate TLS mode for TLSRoute, we want to add conformance tests for both of them. #1579 already tracks conformance tests for TLSRoutes with Passthrough, while this issue aims at tracking conformance tests for TLSRoutes with Terminate mode.

@mlavacca mlavacca added the area/conformance-test Issues or PRs related to Conformance tests. label Nov 21, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 19, 2025
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 21, 2025
@mlavacca
Copy link
Member Author

/remove-lifecycle rotten

/assign

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Mar 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/conformance-test Issues or PRs related to Conformance tests.
Projects
None yet
Development

No branches or pull requests

3 participants