Great video. Can't wait for the letsencrypt one :)
@javagom14 жыл бұрын
(3:40) in order to disable webhook... helm install --name cert-manager --namespace kube-system --set rbac.create=true --set webhook.enabled=false stable/cert-manager
@yigalyiga1667 Жыл бұрын
Love your videos please create more stuff related to k8s
@fastpost50683 жыл бұрын
This is a great video. Thank you!
@trentzhou98975 жыл бұрын
Great talk. It's very helpful. Thank you.
@praveenchandran23555 жыл бұрын
Nice video. In a case where you don't trust your internal network, how do you encrypt the traffic between the ingress and the service itself ? I mean end-to-end encryption ?
@chuchodavidx3 жыл бұрын
how do you modify a command line with vim? I mean, you have something written in your terminal and you jump straight to vim to edit it. How do you do that?
@maureenlofgren8695 Жыл бұрын
How do I https 2 dots on my phone
@LemontJap2k3 жыл бұрын
for the last part, how can we verify using `curl` ? otherwise, nice and very informative helpful video
@MrBlanky6664 жыл бұрын
Great video, thanks!
@tapaschakraborty69946 жыл бұрын
Last step does not create secret for me, also the events are showing blank for me. FYI - It created certificate successfully but not secret. Am I doing something wrong?
@jorgeg35674 жыл бұрын
Very good! Thanks!!!
@elkevindeveloper26304 жыл бұрын
I always ask myself how did he get that knowledge, idk if he has read the RFC of TLS or by reading blogs? does anyone would recommend the best way, I always end by reading RFC but at the end some keyword cannot be understood at all. thanks
@fong5554 жыл бұрын
Great video! Thanks! Do you have any example of spring boot app using embedded tomcat server and deploy to kubernetes work with Https cert? We use keytool java command to export and import key store etc. thanks!
@kubucation4 жыл бұрын
The beauty of containerization and kubernetes is that the processes work regardless of the implementation inside the containers. So, what's shown in the video will also work with a Java/Tomcat based app. You should decide if it's sufficient for your use case that TLS termination happens at the level of the ingress controller (this means traffic inside the cluster is not encrypted). Because then the process outlined here (or a similar one in the GKE ManagedCert video) works without any changes. If you absolutely need TLS termination to happen inside your container (all traffic, even inside the cluster is encrypted) then you can probably still use cert-manager to do so. Cert-manager is mostly an automation tool around completing the required Let's Encrypt challenges. As shown in the vid, the final cert once obtained is saved in a Kubernetes Secret. You can mount this secret (like any other k8s secret) to your application pods if you want. This then means that you effectively have both the private key as well as the .crt file available in your app. I'm not a Java dev (and not familiar with Tomcat), but I assume once you have those files (which is the hard part, as only the CA can sign the Cert) you can easily use them inside your containers. After all, from the perspective of the container (and this is another thing that makes this process so beautiful) it just happens to live in the local file system - without having to know where it came from :) Hope this helps a bit, for further info I'd recommend you to get familiar with the cert-manager docs. Best of luck!
@CNRkl126 ай бұрын
Will it fix tls cert error 509 bunch of ips?
@RA-ir8qd3 жыл бұрын
great vid
@olva6 жыл бұрын
Thank you Soooooooooooooooo Much :)
@maureenlofgren8695 Жыл бұрын
Great video says I won a car
@pizza-cat13374 жыл бұрын
now more simple, cert-manager.io/docs/installation/kubernetes/ Verifying the installation example with self cert