This README provides instructions for verifying EKS cluster including pods, deployments and services. It also includes steps for configuring Keycloak after its installation and generating the admin client credentials to run registry service.
Ensure all pods are running except registry pod and check the service status in your specified namespace.
kubectl get pods -n <namespace>
kubectl get deployments -n <namespace>
kubectl get svc -n <namespace>
The keycloak service will be available in https://
You can use any domain services to get the host name for Sunbird RC. Here, we are going to see how the hostname is configured using Amazon Route53.
kubectl get ingress -n <namespace>
Once you’ve these steps, your Keycloak instance is configured as required. Ensure that the URLs and settings match your specific deployment and use case. Enjoy using Keycloak for your project and begin using Sunbird RC 2.0 Swagger UI.
Keycloak portal will be accessible at https://
Sunbird RC 2.0 registry API portal will be accessible at https://