[Docs] Document how to set up SSL while using pyflyte run on gcloud cluster

[SmritiSatyanV]

Description

Slack conversation User fixed SSL setup while using pyflyte run after setting up their cluster on gcloud. Used the below steps as mentioned in google doc:

Contents of above doc:

1. Follow tutorial upto SSL cert

2. Install certificate manager $ helm repo add jetstack https://charts.jetstack.io $ helm repo update $ kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.9.1/cert-manager.crds.yaml $ helm install cert-manager jetstack/cert-manager --namespace flyte --create-namespace --version v1.9.1

3. Add flyte-certificate.yaml

apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
 name: letsencrypt-production
spec:
 acme:
   server: https://acme-v02.api.letsencrypt.org/directory
   email: <YOUR_EMAIL>
   privateKeySecretRef:
     name: letsencrypt-production
   solvers:
   - selector: {}
     http01:
       ingress:
         class: nginx

4. Add the certificate $ kubectl apply -f flyte-certificate.yaml

5. Continue tutorial from Ingress to installing flyte step 3

6. Modify the values as described, but remove the field for common.ingress.annotations.cert-manager.io/issuer and add cert-manager.io/cluster-issuer: "letsencrypt-production"

7. Continue

Are you sure this issue hasn't been raised already?

• [X] Yes

Have you read the Code of Conduct?

• [X] Yes

[Smartmind12]

@SmritiSatyanV Can you assign this issue to me as i would like to work on it...Thanks!

[Smartmind12]

@SmritiSatyanV Thank you for assigning the issue...I am currently working on it and create a PR once done!

[Smartmind12]

@SmritiSatyanV @cosmicBboy Can you tell me if you would like the document to be editited on Pyflyte or you want a new document to be created ??

[Smartmind12]

@eapolinario @SmritiSatyanV Kindly review the PR and suggest changes if any…Thanks!

[Smartmind12]

@pingsutw & @samhita-alla if possible can you review this PR...Thanks alot!

[github-actions[bot]]

Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. Thank you for your contribution and understanding! 🙏