You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 30, 2023. It is now read-only.
The text was updated successfully, but these errors were encountered:
RomasZekonis
changed the title
Add Support for Azure KeyVault stored certificates for SSL/TLS, maybe
Add Support for Azure KeyVault stored certificates for SSL/TLS, maybe for sshPublicKey also
Nov 12, 2019
This is not an issue. This is maybe more feature request. Sorry maybe I have posted in wrong place.
I think to have a option to bootstrap clusters with TLS certificates stored in keyvault should be useful.
And that would open the way more easy rotate certificates in production deployments, or make it auto-rotatable in the case 3)
@RomasZekonis this is the right place to discuss a feature request 🙂 I'm interested in understanding more about how you envision Azure KeyVault would be integrated with the ARM template offering, and the deployed Elastic Stack.
I could see Azure KeyVault being useful for the three points in #321 (comment).
As far as I know at the moment though, it's not possible to create a KeyVault and insert a certificate into it within an ARM template. , The certificate might need to either already exist in KeyVault, and a secret passed to the template to retrieve it, or a certificate be supplied to the template, and inserted into KeyVault within the installation scripts. There's some complexity involved in both approaches.
I think the one of the option is to pass Certificates Identifier from existing Certificate in the keyvault. We are using the same way deployment of Service Fabric clusters ARM templates. If we deploy with ARM template "Azure Resource Manager for template deployment" should be enabled Access policy of the keyvault.
No description provided.
The text was updated successfully, but these errors were encountered: