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.

Sign up for GitHub

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

Jump to bottom

Conformance tests for TLS Passthrough #1452

Closed
arkodg opened this issue Oct 11, 2022 · 3 comments
Closed

Conformance tests for TLS Passthrough #1452

arkodg opened this issue Oct 11, 2022 · 3 comments
Assignees
@candita
Labels
area/conformance help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
Milestone
v0.6.1

Comments

@arkodg
Copy link
Contributor

arkodg commented Oct 11, 2022

What would you like to be added:
Conformance tests that define rules within the TLS Route API to enable TLS Passthrough between the client and the backend

Why this is needed:
To validate that the implementation supports the TLSRoute API
@arkodg arkodg added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 11, 2022
@arkodg arkodg mentioned this issue Oct 11, 2022
Closed
@shaneutt shaneutt added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. area/conformance labels Oct 12, 2022
@shaneutt shaneutt added this to the v0.7.0 milestone Oct 12, 2022
@shaneutt shaneutt modified the milestones: v0.7.0, v0.6.1 Nov 2, 2022
@candita
Copy link
Contributor

candita commented Nov 17, 2022

@shaneutt I'll get this started.

@candita
Copy link
Contributor

candita commented Dec 5, 2022

See #1579 for a comprehensive list of tests that we can prioritize.

@shaneutt
Copy link
Member

shaneutt commented Dec 5, 2022

Sounds good, since #1579 seems to cover the purpose of this issue but has a long list of the individual tests to create, I'll close this as a duplicate. @arkodg if you feel that there's any context this issue has that isn't properly captured by #1579 let me know.

@shaneutt shaneutt closed this as not planned Won't fix, can't repro, duplicate, stale Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@candita candita

Labels
area/conformance help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
v0.6.1
Development

No branches or pull requests
3 participants
@candita @shaneutt @arkodg