Thanks for the video! I'm seeing that you are having some failures with editing the vault-internal service that you cut from the video. I'm also having this error following along with the video. What did you do behind the scenes to make that work? Thanks
You see it in the video. I got the same error. You have to delete the lines with clusterIP and change the type to NodePort. Kubernetes does not let you and say it is saved to a file. Then like in the video kubectl delete -f file and kubectl apply -f file. And then you will have the NodePort.
Can an External Storage be hooked with Hasicorp Vault. Like External Secret Operator (ESO) offer association with various external storage provider
Very well explained! Thank you.
Very good explanation
Great video,
I have a query. with this method, still the secrets can be decoded at the kubernetes end right? So is this secure enough?
Nice 👍
gr888 session
HI, Thanks for this video, is this the same as csi -secret store provider driver in one of your other videos ?
No this is different, if you see the demo portion, it shows how this one works.
Thanks for the video! I'm seeing that you are having some failures with editing the vault-internal service that you cut from the video. I'm also having this error following along with the video. What did you do behind the scenes to make that work? Thanks
Did you try from the Repo ?
You see it in the video. I got the same error. You have to delete the lines with clusterIP and change the type to NodePort. Kubernetes does not let you and say it is saved to a file. Then like in the video kubectl delete -f file and kubectl apply -f file. And then you will have the NodePort.