For this example we expose artifactory service with an nginx deployment and an Load Balancer service.
There are many ways to terminate ssl on kubernetes including ingress, L7 load balancing. For this release, because we will be deploying on GKE with loadBalancer type, GKE will allocate the LB for us. However, since the load balancer is a layer-4 loadBalancer only, thus we will not be terminating the ssl on LB but on our nginx deployment.
There are many ways to terminate ssl on kubernetes including ingress, L7 load balancing. For this release, because we will be deploying on GKE with loadBalancer type, GKE will allocate the LB for us. However, since the load balancer is a layer-4 loadBalancer only, thus we will not be terminating the ssl on LB but on our nginx deployment.
$ helm install artifactory-ha \ --set nginx.enabled=false \ --set nginx.tlsSecretName=artifactory-tls \ --set nginx.replicaCount: 2 \ --set nginx.resources.requests.cpu="100m" \ --set nginx.resources.limits.cpu="250m" \ --set nginx.resources.requests.memory="250Mi" \ --set nginx.resources.limits.memory="500Mi" \ --namespace artifactory-ha jfrog/artifactory-ha --version 107.21.12 --dry-runWe will add the properties above to a values.yaml
nginx: enabled: true tlsSecretName: artifactory-tls replicaCount: 2 resources: requests: cpu: 100m memory: 250Mi limits: cpu: 250m memory: 500Mi