Setup Kubernetes Registry Secret

Create a Kubernetes docker-registry secret for GitLab image pulls.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/billynewport/demo_cokub_model --skill setup-kubernetes-registry-secret
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Setup Kubernetes Registry Secret
Source: https://github.com/billynewport/demo_cokub_model/tree/main/.claude/skills/setup-k8s-registry-secret
Command: npx skills add https://github.com/billynewport/demo_cokub_model --skill setup-kubernetes-registry-secret

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill configures a Kubernetes image pull secret to access the GitLab container registry for DataSurface images, enabling seamless deployment without manual credential management.

Core Features & Use Cases

  • Secret creation: Create a docker-registry secret that stores GitLab credentials for image pulls.
  • Namespace scoping: Apply the secret to a specific namespace and attach it to the default service account for automatic image pulls.
  • Operational use: Use in Kubernetes deployments and Helm charts to ensure private registry access with minimal configuration.

Quick Start

Run the kubectl commands to create the docker-registry secret and attach it to the default service account in the target namespace.

Frequently Asked Questions about Setup Kubernetes Registry Secret

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

FAQPage Schema
How do I create a Kubernetes secret to pull images from a private GitLab container registry?

To create a Kubernetes image pull secret for a GitLab container registry, use kubectl to generate a docker-registry secret with your GitLab deploy token credentials. This stores your username and token securely for private image pulls.

How do I bind a docker-registry secret to a service account so pods can pull private images?

Binding a docker-registry secret to the default service account allows Kubernetes pods to automatically authenticate private registry pulls. You attach the secret to the default service account within a specified namespace using kubectl.

What do I need to configure Kubernetes imagePullSecrets for a GitLab deploy token?

Configuring imagePullSecrets requires kubectl, a GitLab deploy token with its username and token values, and environment variables. These inputs create and manage the docker-registry secret for accessing private DataSurface images.

Can I scope a Kubernetes image pull secret to a specific namespace for GitLab registry access?

Yes, you can apply the docker-registry secret to a specific namespace. This ensures the GitLab container registry credentials are scoped appropriately and attached to the default service account within that namespace.

Why are my Kubernetes pods failing to pull images from the GitLab container registry?

Kubernetes pods fail to pull GitLab container registry images when missing valid imagePullSecrets. Creating a docker-registry secret with a valid GitLab deploy token and binding it to the default service account resolves authentication failures.