Today I mainly be tinkering with RedHat OpenShift Container Platform (OCP) on IBM Cloud, and am running through a set of steps that I've written to document the end-to-end setup.
Having created a cluster on Friday, I tried to authenticate to it today: -
export apikey="my_api_key_goes_here"
oc login https://control-plane-endpoint-url:31452 -u apikey -p $apikey
but this threw up: -
Error from server (InternalError): Internal error occurred: unexpected response: 500
After a spot of digging, I realised why this was the case.
This was a newly created cluster BUT I'd not yet retrieved the cluster configuration from IBM Cloud.
The cluster name is roks-oct2021 so I needed to run: -
ic cs cluster config --cluster roks-oct2021
OK
The configuration for roks-oct2021 was downloaded successfully.
Added context for roks-oct2021 to the current kubeconfig file.
You can now execute 'kubectl' commands against your cluster. For example, run 'kubectl get nodes'.
If you are accessing the cluster for the first time, 'kubectl' commands might fail for a few seconds while RBAC synchronizes.
Once I'd done this, all was well - I was able to run: -
oc login https://control-plane-endpoint-url:31452 -u apikey -p $apikey
which responded: -
Login successful.
You have access to 66 projects, the list has been suppressed. You can list all projects with 'oc projects'
Using project "default".
No comments:
Post a Comment