Pods never become ready.

This document (7023467) is provided subject to the disclaimer at the end of this document.

Environment

SUSE CaaS Platform
SUSE Cloud

Situation

The following pods never become to ready, even after waiting for hours :

router-0
routing-api-0
tcp-router-0

Resolution

Create DNS records to point to one of the worker nodes defined in the file : scf-config-values.yaml

api.$fqdn
doppler.$fqdn
login.$fqdn
uaa.$fqdn scf.uaa.$fqdn
ssh.$fqdn

(Where '$fqdn' would be your fully qualified domain name).

Cause

The pods just never transition to ready, and the root cause is usually because DNS is not set up correctly.

These rules have to be configured before the SCF helm chart is deployed. However, once the SCF helm chart has already been deployed, the kubernetes cluster may need to be rebuilt.

Additional Information

The documentation link below describe how to create the file scf-config-values.yaml :

https://www.suse.com/documentation/cloud-application-platform-1/singlehtml/book_cap_deployment/book_cap_deployment.html#sec.cap.addrepo-prod

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.