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

It is possible to have several CAs within the same cluster. #153

Open
Fr0zenBoy opened this issue May 5, 2022 · 4 comments
Open

It is possible to have several CAs within the same cluster. #153

Fr0zenBoy opened this issue May 5, 2022 · 4 comments

Comments

@Fr0zenBoy
Copy link

Fr0zenBoy commented May 5, 2022

Is it possible to have more than one CA within istio-csr? How do configure it?

The second question is how can I configure which CA my sidecar will get certificates through annotations or some declaration method? I need to configure the CA that each pod will use to communicate from pod to pod.

I'm using aws pca external issuer.

@marcingy
Copy link
Contributor

marcingy commented Jun 2, 2022

I have a similar question related to having a CA for each mesh that we have in a cluster. The intent is too potential highly isolate some workloads.

@kuberkaul
Copy link

have the same question, is it possible to set multiple cluster issuers in istio-csr(using AWS PCA) ?

@SgtCoDFish
Copy link
Member

Hey, thanks for raising this (and sorry it took a year to get a response 😭 )

We'd been looking into something like this internally at Venafi. There might be some scope for us to work on this. Our motivation is to enable istio-csr to be installed without having a CA configured (since currently the issuing CA has to be passed at container startup). That would enable users to install istio-csr alongside cert-manager without needing to configure a CA first.

One thing we'd considered (but not in depth) was to allow the CA to be configured per-namespace, e.g. with a IstioCSRNamespaceBinding resource. Would that solve the problems here, or is per-pod a requirement?

Kuber and I had spoken on K8s slack also, around being able to trust two CAs. That's definitely something we should capture too!

@solidDoWant
Copy link

Would that solve the problems here, or is per-pod a requirement?

This would be great (for me at least).

One other area that having support for multiple CAs would be great for is having a separate CA for the listener interface, and for the actual Istio certs. Currently I have a separate per-namespace intermediary CA, which I use for server auth for anything that requires it. When deploying Istio and istio-csr, I'd like to be able to use a separate Istio-only CA for Istio mesh services.

I may be interested in filing a PR for this feature, if a PR would be accepted for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants