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

Design/document the contract for Serving Encryption #13819

Open
4 tasks
ReToCode opened this issue Mar 29, 2023 · 3 comments
Open
4 tasks

Design/document the contract for Serving Encryption #13819

ReToCode opened this issue Mar 29, 2023 · 3 comments
Labels
area/networking kind/spec Discussion of how a feature should be exposed to customers. triage/accepted Issues which should be fixed (post-triage)

Comments

@ReToCode
Copy link
Member

ReToCode commented Mar 29, 2023

Description

Discuss/design the contract for cluster-local and Knative internal encryption.

Tasks

  • Draft a design contract for cluster-local and Knative internal encryption with changes to the Knative specification (if needed)
  • Update the Knative specification in code & docs
  • Create/Update conformance tests for networking implementations
  • Add e2e tests in serving to enforce encryption + a full CA rotation

Related work

/area networking
/kind spec

@knative-prow knative-prow bot added area/networking kind/spec Discussion of how a feature should be exposed to customers. labels Mar 29, 2023
@ReToCode ReToCode added the triage/accepted Issues which should be fixed (post-triage) label Mar 29, 2023
@ReToCode
Copy link
Member Author

/cc @davidhadas

@davidhadas
Copy link
Contributor

@ReToCode ReToCode changed the title Design and implement the contract for internal-encryption Design the contract for cluster-local and knative-internal encryption Aug 3, 2023
@ReToCode
Copy link
Member Author

ReToCode commented Aug 3, 2023

Related: #13819

@ReToCode ReToCode changed the title Design the contract for cluster-local and knative-internal encryption Design/document the contract for Serving Encryption Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/networking kind/spec Discussion of how a feature should be exposed to customers. triage/accepted Issues which should be fixed (post-triage)
Projects
Status: No status
Development

No branches or pull requests

2 participants