[GitHub] [apisix-helm-chart] gardun0 commented on issue #230: Request help: how to setup the gateway variables to enable HTTPS?

[GitBox <gi...@apache.org>]

gardun0 commented on issue #230:
URL: https://github.com/apache/apisix-helm-chart/issues/230#issuecomment-1029327166


   Hey @MirtoBusico, in order to secure your gateway, there are many methods out there, this is one of them:
   
   1. Enable TLS with `gateway.tls.enabled` set to `true`, this will add a `443` port for your service.
   2. In order to expose your gateway, you must set the service to `LoadBalancer` type (alternative to Ingress).
   3. As soon as your service set up, it'll have a public address with two ports `80` and `443`.
   4. In order to have a TLS/SSL certificate there are many ways to do that but Let's Encrypt might do that Job for you, in this case we're using [cert-manager](https://cert-manager.io/).
   5. You must set up an `Issuer`/`ClusterIssuer` with [cert-manager](https://cert-manager.io/) and a `Certificate`, that `Certificate` will generate a secret including the keys within your namespace (I don't remember if it must be the same as Apisix).
   6. Once you have a `Certificate` resource created, you must create an `ApisixTls` resource referencing the same DNS you set on your `Certificate` and the secret name generated.
   7. Finally you must change your domain DNS with the one generated trough your `LoadBalancer`.
   
   Overall, this is a simple guide to secure your exposed gateway (I may missed something)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org