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

TLS verification feature user-acceptance testing #6633

Open
2 tasks
Tracked by #6374
czeslavo opened this issue Nov 7, 2024 · 1 comment
Open
2 tasks
Tracked by #6374

TLS verification feature user-acceptance testing #6633

czeslavo opened this issue Nov 7, 2024 · 1 comment
Labels
area/tests blocked release/required it is required that this be resolved before releasing
Milestone
KIC v3.4.x

Comments

@czeslavo
Copy link
Contributor

czeslavo commented Nov 7, 2024 •
edited
Loading

This issue aims to cover the upstream TLS verification feature both for Gateway API policy and Ingress annotations.

Acceptance criteria

  • Somebody who wasn't involved directly in the feature development has verified the guide works as expected
  • The same person tried to break the feature triggering edge-case scenarios
@czeslavo czeslavo mentioned this issue Nov 7, 2024
Open
2 tasks
@czeslavo czeslavo added this to the KIC v3.4.x milestone Nov 7, 2024
@lahabana lahabana added release/required it is required that this be resolved before releasing blocked labels Nov 12, 2024
@lahabana
Copy link
Contributor

Blocked on the rest of the implementation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/tests blocked release/required it is required that this be resolved before releasing
Projects
None yet
Milestone
KIC v3.4.x
Development

No branches or pull requests
2 participants
@lahabana @czeslavo