(Private artifact registry only) Create a pull-secret manifest for the private artifact registry

Introduction

If the private artifact registry requires authentication (that is, you must provide credentials to access the registry), you must create a pull-secret manifest for authenticating to the registry. Typically, a private artifact registry in an air-gapped cluster doesn’t require authentication.

How the pull-secret manifest is used

When you later perform a clean installation of the CNE core and CNE instances (each in its own namespace), you’ll use the pull-secret manifest to create a pull secret for the private artifact registry in each namespace. Kubernetes uses the private artifact registry’s pull secret to authenticate to the private artifact registry when pulling Docker container images from it.

Create a pull-secret manifest for authenticating to the private artifact registry

  1. In a terminal window on your computer, make sure you’re in the release-manifest directory, which contains the release manifest (bigip-k8s-manifest-<VERSION>.yaml).

  2. Create the private artifact registry’s pull-secret manifest.

    Note

    You can use any name you like for the pull secret except far-pull-secret, which is reserved as the name of the F5 Artifact Registry pull secret.

    Most artifact registries can provide you with a pull-secret manifest, which looks like this for a pull secret named private-registry-pull-secret:

    apiVersion: v1
kind: Secret
metadata:
  name: private-registry-pull-secret
data:
  .dockerconfigjson: eyJodHRwczovL2luZGV4L...J0QUl6RTIifX0=
type: kubernetes.io/dockerconfigjson

    If your registry can’t provide you with a pull-secret manifest, see Pull an Image from a Private Registry.