"Failed to get repository versions: rate limit for github api has been reached" error when creating/deleting CSE clusters in VMware Cloud Director.
search cancel

"Failed to get repository versions: rate limit for github api has been reached" error when creating/deleting CSE clusters in VMware Cloud Director.

book

Article ID: 325644

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

Symptoms:
  • When deploying/deleting TKG CSE clusters,the clusters result in a state of "Error".
  • The following error is displayed in the Cloud Director UI and in the Ephemeral VM log /var/log/cloud-final.err after completing a create cluster/delete cluster task: 

Error: failed to get provider components for the "cluster-api:v1.1.3" provider: failed to get repository client for the CoreProvider with name cluster-api: error creating the GitHub repository client: failed to get GitHub latest version: failed to get repository versions: failed to get repository versions: rate limit for github api has been reached. Please wait one hour or get a personal API token and assign it to the GITHUB_TOKEN environment variable.


Environment

VMware Cloud Director 10.x

Cause

  • This error states that the environment is reaching a rate limit when completing CSE operations.
  • CSE has a limit on the amount of requests which can be made without a valid GitHub personal access token.

Resolution

To resolve this error,set a GitHub personal access token to CSE configuration:
1. Note your Github Personal Access Token.Refer GitHub documentation to Create a Personal Access Token.
2. From the Provider view, Click More in the top tab.
3. Select Kubernetes Container Clusters from the drop down list.
4. Click the CSE Management Tab.
5. Click Server Details on the left pane.
6. Click Update server.
7. Provide the GitHub token in the respective field. 
8. After updating the CSE configuration, please restart the CSE server.


Additional Information

Impact/Risks:
When the CSE API request limit is reached,the various tasks initiated in Cloud Director against any existing or creating new clusters will result in error.