• dudeami0@lemmy.dudeami.win
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    Hard to believe you used to have to pay for a TLS certificate. I use Let’s Encrypt with cert-manager on my kubernetes cluster and it still amazes me how SSL just happens. Even just using certbot makes the job extremely simple.

    • sudneo@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      For cert-manager to work you need to have the ingress controller port (or I guess another port) exposed publicly? Or it supports DNS verification? I thought about doing this, but I am essentially having my cluster fully in a private network which I connect with wireguard from outside, but maybe I should reconsider?

      I am keen to know a little bit more about your setup

      • dudeami0@lemmy.dudeami.win
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        I am using cloudflare DNS, which cert-manager requires an API key to edit the DNS entries. Documentation on this can be found here. It seems to support a number of DNS APIs, you can view those here.

    • HTTP_404_NotFound@lemmyonline.com
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      And what is worse-

      It wasn’t cheap either! Some of the SSL cert providers were charging hundreds/thousands for a certificate!

      The less evil ones, were still charging 30$ or so.

    • ActuallyRuben@actuallyruben.nl
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      There even are still some (shitty) webhosts that require payment for a TLS certificate, because they refuse to support letsencrypt.