You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
Rancher 2 v2.1.1 display the status This cluster is currently Waiting; areas that interact directly with it will not be available until the API is ready. Waiting for API to be available
workaround
There is a workaround :
change stable by v2.0.7 in cdk-rancher-nodeport.yaml and apply it to deploy v2.0.7 (this version is OK)
then change v2.0.7 by v2.1.1 or stable in cdk-rancher-nodeport.yaml and apply it to deploy v2.1.1
The text was updated successfully, but these errors were encountered:
Sorry for the delay - we are aware of this issue and I am working directly with Rancher to solve the issue. Expect a change to this repo in the next week or so.
Cheers
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue
I deployed a kubernetes-core cluster v1.11 cluster with Conjure up on LXD.
I deployed Rancher 2 on top of K8s cluster
Rancher 2 v2.1.1 display the status
This cluster is currently Waiting; areas that interact directly with it will not be available until the API is ready. Waiting for API to be available
workaround
There is a workaround :
The text was updated successfully, but these errors were encountered: