secrets

Generate Kubernetes docker-registry Secrets and ServiceAccounts for container registry authentication.

35|38|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/IBM/bob-demo --skill secrets-ibm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secrets
Source: https://github.com/IBM/bob-demo/tree/main/tekton-devops/input-documents/hello-world-tekton/skills/secrets
Command: npx skills add https://github.com/IBM/bob-demo --skill secrets-ibm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates creation of the Kubernetes manifests required to authenticate to private container registries so CI/CD pipelines and cluster workloads can pull images without manual secret creation.

Core Features & Use Cases

  • Generate docker registry Secret: produce a kubernetes.io/dockerconfigjson payload and encode it in base64 for registry authentication.
  • Create ServiceAccount: emit a ServiceAccount manifest that references the created Secret so build agents can use the credentials.
  • Pipeline compatibility: include registry annotations compatible with Tekton and other pipeline controllers to locate registry credentials. Use case: produce separate Secret and ServiceAccount manifests to enable a Tekton pipeline to pull images from a private registry.

Quick Start

Generate a Kubernetes Secret with a base64-encoded dockerconfigjson for registry host registry.example.com using username alice and password s3cr3t and create a ServiceAccount named build-bot that references that secret.

Frequently Asked Questions about secrets

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

FAQPage Schema
How do I create a Kubernetes docker-registry secret for pulling private images?

To create a Kubernetes docker-registry secret, you generate a kubernetes.io/dockerconfigjson payload encoded in base64 containing your registry credentials, then emit it as a Secret manifest for cluster authentication.

Can I generate a ServiceAccount that references a docker-registry secret for Tekton pipelines?

Yes, you can generate a ServiceAccount manifest that references your created docker-registry Secret, allowing Tekton pipeline build agents to authenticate and pull images from private container registries.

What's the best way to set up registry authentication for Kubernetes CI/CD builds?

Setting up registry authentication for Kubernetes CI/CD builds involves creating a base64-encoded dockerconfigjson Secret and an associated ServiceAccount, adding Tekton registry annotations to help controllers locate credentials.

Does Tekton require specific annotations to use docker-registry secrets in pipelines?

Tekton pipelines use tekton.dev registry annotations on the generated ServiceAccount to locate and apply docker-registry credentials, ensuring build agents can pull authenticated container images during pipeline execution.

When do I need a dockerconfigjson secret in Kubernetes?

You need a dockerconfigjson secret in Kubernetes when cluster workloads or CI/CD pipelines must pull container images from private, authenticated registries instead of public ones.

Are separate manifest files generated for the Kubernetes Secret and ServiceAccount?

Yes, the generation process outputs separate manifest files for the docker-registry Secret and the associated ServiceAccount, keeping the Kubernetes resource definitions isolated for easier management.