Runtime Fabric Pull Secret Creation Command on Podman or Containerd, Not Just Docker

APPLIES TO: Runtime Fabric (self-managed, on-premises or GKE/OpenShift installs), image pull secret configuration

ISSUE: Runtime Fabric installation documentation shows creating an image pull secret with the command: kubectl create secret docker-registry <secret-name> --docker-server=<registry> --docker-username=<user> --docker-password=<password>

Teams whose container runtime is Podman or containerd (rather than Docker) sometimes assume this command requires a Docker CLI or Docker daemon to be present, or that an equivalent Podman-specific command is needed instead.

CAUSE: "docker-registry" in this command is the NAME of a built-in Kubernetes secret type, not a reference to the Docker CLI or Docker daemon. The kubectl create secret docker-registry command talks directly to the Kubernetes API server to create a secret of that type. It does not invoke, require, or depend on any local container runtime at all.