Use ca.NewCA() for generating certs and keys for the proxy injector#2163
Use ca.NewCA() for generating certs and keys for the proxy injector#2163
ca.NewCA() for generating certs and keys for the proxy injector#2163Conversation
6ae8d62 to
0ed4083
Compare
|
Should the This isn't a blocker, just an organizational note. |
|
@ver yea, |
klingerf
left a comment
There was a problem hiding this comment.
This looks like the right approach to me. I'd love to see some refactoring here to allow the proxy-injector to use as much of the generic CA code as possible, and I called that out in my comments below.
|
My last push is broken into 4 commits like so:
Let me know what you think 🙏 |
klingerf
left a comment
There was a problem hiding this comment.
⭐️ Looks great, thanks for updating!
Fixes #2095 Signed-off-by: Alejandro Pedraza <[email protected]>
Signed-off-by: Alejandro Pedraza <[email protected]>
Signed-off-by: Alejandro Pedraza <[email protected]>
- Remove from CA controller everything that dealt with the webhook/proxy-injector - Remove no longer needed proxy-injector volumes for 'trust-anchors' and 'webhook-secrets' - Remove from the proxy-injector the retrieval of the trust anchor and secrets Signed-off-by: Alejandro Pedraza <[email protected]>
Signed-off-by: Alejandro Pedraza <[email protected]>
Signed-off-by: Alejandro Pedraza <[email protected]>
Signed-off-by: Alejandro Pedraza <[email protected]>
Signed-off-by: Alejandro Pedraza <[email protected]>
Signed-off-by: Alejandro Pedraza <[email protected]>
Signed-off-by: Alejandro Pedraza <[email protected]>
16f6399 to
118764b
Compare

Use
ca.NewCA()for generating certs and keys for the proxy injector instead of grabbing the trust anchor from the linkerd-ca-bundle ConfigMap, as well as avoiding having to watch linkerd-proxy-injector-service-tls-linkerd-io secrets for the cert and key used for the injector's TLS server.This is just a POC. If this approach is accepted, the next step is to remove all the code that was dealing with those secrets.
Fixes #2095