PR 167, which addressed issue 166 , brought support for distributing externally created TLS material to Pravega Pods via Kubernetes secrets to Pravega Operator managed deployments. Currently, that mechanism allows for using a single set of TLS material per type:
All Controller instances/pods share the same TLS certificate and other material.
All Segment store instances/pods share the same TLS certificate and other material.
Requirement:
Add support for distributing and using instance/pod-specific TLS material, such that each Segment Store and Controller Pod uses its own set of TLS material.
Background:
PR 167, which addressed issue 166 , brought support for distributing externally created TLS material to Pravega Pods via Kubernetes secrets to Pravega Operator managed deployments. Currently, that mechanism allows for using a single set of TLS material per type:
Requirement:
Add support for distributing and using instance/pod-specific TLS material, such that each Segment Store and Controller Pod uses its own set of TLS material.