A DevOps project user can configure credentials for Jenkins Pipeline. Once a user (e.g. Owner and Maintainer) adds/configures these credentials in DevOps project, the credentials can be used by DevOps projects to interact with these third-party applications.
Currently, it can store the following 4 types of credentials in DevOps project:
Sign in with
project-regular, choose Credentials and click Create Credential.
Click Create, fill in the basic information in the pop-up window.
Credential ID: it will be used in pipeline, name it dockerhub-id
Username: Your DockerHub account
Token/password: Your DockerHub password
Description: A brief introduction to this credential.
Click OK when you've done.
Similarly, we create a GitHub Credential and name it
github-id, choose Account Credentials, others are the same with above.
Note: If there is any special characters includes
$, it may cause unrecognizable error. You need to encode your account or password through third-party website, e.g. urlencoder, please convert it and paste to KubeSphere console.
The same as above, create a Credential, name it
demo-kubeconfig, choose kubeconfig, click Create to complete creation.
Note: A file that is used to configure access to clusters is called a kubeconfig file. Thus we create the kubeconfig credential to access the current Kubernetes cluster, which will be used in pipeline. You don't need to change the file since KubeSphere will automatically load the kubeconfig of the current Kubernetes cluster. On the contrary, you may need to change kubeconfig in KubeSphere when access other cluster.
At this point, you can return to the quick start guides to complete the rest steps.
Enter this credential's details page, then you can edit its information or delete it.