(F5 Artifact Registry only) Create a pull-secret manifest for the F5 Artifact Registry

Introduction

If you did not store Helm charts and Docker container images in a private artifact registry, you must create a pull-secret manifest for authenticating to F5 Artifact Registry. F5 Artifact Registry always requires 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 F5 Artifact Registry in each namespace. Kubernetes uses the F5 Artifact Registry’s pull secret to authenticate to F5 Artifact Registry when pulling Docker container images from it.

Create a manifest for the F5 Artifact Registry pull secret

Note

If you stored Helm charts and Docker container images in a private artifact registry, skip this task. You already created a manifest for your private artifact registry’s pull secret and don’t need a manifest for the F5 Artifact Registry pull secret.

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 a manifest for the F5 Artifact Registry pull secret:

   cat <<EOF > far-pull-secret.yaml
   ---
   apiVersion: v1
   kind: Secret
   metadata:
     name: far-pull-secret
   data:
     .dockerconfigjson: $(echo '{"auths": {"repo.f5.com": {"auth": "'$(echo "_json_key_base64:$(cat ../cne_pull_64.json)" | base64 -w 0)'"}}}' \
       | base64 -w 0)
   type: kubernetes.io/dockerconfigjson
   EOF
   

   The command creates a file named far-pull-secret.yaml in the release-manifest directory.

Next steps

• To begin the installation, go to Install.