2

When running setup_robot.sh per the Cloud Robotics documentation, the certificate is not valid. I get the following error:

Failed to update robot CR my-robot: Failed to get robot my-robot: Get https://www.endpoints.robco-skopecki.cloud.goog/apis/core.kubernetes/apis/registry.cloudrobotics.com/v1alpha1/namespaces/default/robots/my-robot: x509: certificate is valid for ingress.local, not www.endpoints.robco-skopecki.cloud.goog
Misha Brukman
  • 12,938
  • 4
  • 61
  • 78
Steffen
  • 23
  • 3

1 Answers1

2

This problem occurs if letsencrypt did not finish creating the certificate for the cloud-cluster. This might happend during a first time install. Here is how you can check:

kubectl get certificates cloud-robotics -o yaml

If the output lacks a status, restart the cert-manager:

kubectl delete pod cert-manager-<tab>

Once it restarted, check the certificate again and once the status is indicating sucess, you should have your certificate stored as a secret called tls:

kubectl get secrets tls

At this point you can rerun setup_robot.sh.

ensonic
  • 3,304
  • 20
  • 31