kubesphere-devops-credentials

Convert Kubernetes Secrets into Jenkins-compatible credentials for KubeSphere DevOps.

17.0k|2.8k|Updated Apr 21, 2018
One-click install
npx skills add https://github.com/kubesphere/kubesphere --skill kubesphere-devops-credentials
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kubesphere-devops-credentials
Source: https://github.com/kubesphere/kubesphere/tree/main/skills/kubesphere-devops-credentials
Command: npx skills add https://github.com/kubesphere/kubesphere --skill kubesphere-devops-credentials

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralize and secure access to credentials used in KubeSphere DevOps across projects, ensuring secrets are properly labeled, synced to Jenkins, and consumable by pipelines and Git workflows.

Core Features & Use Cases

  • Credential types supported include SSH, Basic Auth, Secret Text, and Kubeconfig (where supported), enabling seamless integration with Git repositories, deployments, and API tokens.
  • Credentials are stored as Kubernetes Secrets with DevOps labels and are designed to be referenced by GitRepository, Pipelines, and Jenkins, simplifying credential management and rotation.
  • API endpoints for credential lifecycle (list, create, get, update, delete, usage) and the workflow for linking credentials to GitRepository and pipelines.

Quick Start

Create a credentials secret, link it to a GitRepository, and reference it in a Pipeline to enable secure DevOps access.

Frequently Asked Questions about kubesphere-devops-credentials

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Jenkins credentials in KubeSphere DevOps pipelines?

You can manage Jenkins credentials in KubeSphere DevOps by creating Kubernetes Secrets with specific DevOps labels, which are then synchronized to Jenkins for use across your pipelines. This centralizes secure access for Git and deployments.

What types of credentials are supported for Git access in KubeSphere DevOps?

Supported credential types for Git access in KubeSphere DevOps include SSH, Basic Auth, Secret Text, and Kubeconfig. These are stored as Kubernetes Secrets and can be linked directly to GitRepository workflows.

How do Kubernetes Secrets sync to Jenkins for DevOps pipelines?

Kubernetes Secrets sync to Jenkins when they are configured with the required credential.devops.kubesphere.io/* type and DevOps labels. This synchronization process exposes them as Jenkins-compatible credentials for pipeline consumption.

Can I use KubeSphere DevOps credentials with ArgoCD workflows?

Yes, KubeSphere DevOps credentials can be linked to ArgoCD workflows. The credentials stored as Kubernetes Secrets are designed to be referenced across DevOps projects for Git access and deployments.

What is the API workflow for credential lifecycle management in KubeSphere?

The API workflow for credential lifecycle management in KubeSphere exposes REST endpoints to list, create, get, update, delete, and check usage. This allows automated management of DevOps credentials across projects.

Do I need specific labels on Kubernetes Secrets for KubeSphere DevOps?

Yes, Kubernetes Secrets must have specific DevOps labels and the required Secret type credential.devops.kubesphere.io/* to be recognized by KubeSphere DevOps. This ensures proper synchronization to Jenkins.