Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RP installation - cert/TLS file not working #166

Open
ghost opened this issue May 1, 2021 · 3 comments
Open

RP installation - cert/TLS file not working #166

ghost opened this issue May 1, 2021 · 3 comments

Comments

@ghost
Copy link

ghost commented May 1, 2021

"kubernetesVersion": "1.19.9"
helm version
version.BuildInfo{Version:"v3.4.1", GitCommit:"c4e74854886b2efe3321e185578e6db9be0a6e29", GitTreeState:"clean", GoVersion:"go1.14.11"}

Steps followed:

  1. helm install reportportal-ingress --namespace report-portal stable/nginx-ingress
  2. kubectl get service --namespace="report-portal"
    Updated Values.yaml -> ingress.hosts - with <LoadBalancer's EXTERNAL-IP address>
  3. helm repo add elastic https://helm.elastic.co && helm repo update
  4. helm dependency build ./reportportal/
  5. helm install elasticsearch-chart --namespace="report-portal" --set replicas=1 ./reportportal/charts/elasticsearch-7.6.1.tgz [1 replica - as i have 1 node cluster]
  6. helm install rabbitmq-chart --namespace="report-portal" --set auth.username=rabbitmq,auth.password=rmq_password,replicaCount=1 ./reportportal/charts/rabbitmq-7.5.6.tgz
  7. kubectl exec -it rabbitmq-chart-0 --namespace="report-portal" -- rabbitmqctl set_vm_memory_high_watermark 0.8
  8. helm install postgresql-chart --namespace="report-portal" --set postgresqlUsername=rpuser,postgresqlPassword=rpuser_password,postgresqlDatabase=reportportal,postgresqlPostgresPassword=postgres_password -f ./reportportal/postgresql/values.yaml ./reportportal/charts/postgresql-8.6.2.tgz
  9. helm install minio --namespace="report-portal" --set accessKey=minio_accesskey,secretKey=minio_secretkey,persistence.size=40Gi stable/minio
  10. kubectl get pods --namespace="report-portal"
  11. kubectl get service --namespace="report-portal"
  12. helm package ./reportportal/
  13. helm install reportportal-chart --namespace="report-portal" --set postgresql.SecretName=postgresql-chart,rabbitmq.SecretName=rabbitmq-chart ./reportportal-5.3.5.tgz
  14. kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.3/cert-manager.crds.yaml
  15. helm repo add jetstack https://charts.jetstack.io && helm repo update
  16. helm install cert-manager jetstack/cert-manager --namespace="report-portal" --version v1.0.3
  17. Created letsencrypt-clusterissuer.yaml in my local machine. and ran the below command:
    kubectl apply -f letsencrypt-clusterissuer.yaml --namespace="report-portal"

letsencrypt-clusterissuer.txt

  1. helm upgrade reportportal-chart --namespace="report-portal" -f reportportal/values.yaml --set installCRDs=true --set postgresql.SecretName=postgresql-chart,rabbitmq.SecretName=rabbitmq-chart ./reportportal-5.3.5.tgz

values.txt

After this is was able to lauch the URL https://51.105.219.36/ui/#login and login using default/1q2w3e - but it said the site it not secure:
MicrosoftTeams-image

Hence I proceeded with the next step of adding TLS. But I'm getting an error

  1. kubectl apply --namespace="report-portal" -f certificate-tls.yaml - Failed
    Getting Error:
    no matches for kind "Certificate" in version "certmanager.k8s.io/v1alpha1"

here is the gateway ingress file and the tls file:
gateway-ingress.txt

Certificate-tls.yaml file.
certificate-tls.txt

Please help me fix this and Do let me know if there r any mismatch in the versions I'm using?
Also, every next day when I log in to work - I see all the pods would have crashed. is there any parameter to let them run forever?

Thanks in advance.

@samagarw
Copy link

Facing same issue . Did anyone find the solution for this .

@vitaliirymar
Copy link

Facing same issue . Did anyone find the solution for this?

@Jmainguy
Copy link

The solution is to properly configure cert-manager to use a real issuer. The screenshot above shows it is using a fake issuer (by default this is normal). Everyone uses different Cert providers, which require credentials and other ways of proving it should issue you a cert. https://cert-manager.io/ explains in great detail how to use it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants