Enable CryptoMB PrivateKeyProvider extension#3752
Conversation
Co-authored-by: Ismo Puustinen <ismo.puustinen@intel.com>
|
😊 Welcome @rveerama1! This is either your first contribution to the Istio proxy repo, or it's been You can learn more about the Istio working groups, code of conduct, and contributing guidelines Thanks for contributing! Courtesy of your friendly welcome wagon. |
|
Hi @rveerama1. Thanks for your PR. I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/ok-to-test |
|
/retest |
lambdai
left a comment
There was a problem hiding this comment.
It's ok to me that the proxy build with this contrib extension.
I have concern whether to introduce istio api on top of contrib feature, but it is discussed in istio/api issue
What this PR does / why we need it:
Envoy cryptomb contrib extension is an extension which brings tls private key providers features to Istio.
Currently, it can be activated via ProxyConfig in Istio service-mesh environment, the config looks like below:
To set the mesh wide defaults, configure the
defaultConfigsection ofmeshConfig. For example:This can also be configured on a per-workload basis by configuring the
proxy.istio.io/configannotation on the pod.For example:
istio-api addition PR: istio/api#2261
istio related changes PR: istio/istio#37681