(Private artifact registry only) Store charts and images in a private artifact registry¶

Introduction¶

The following instructions describe how to store Helm charts and Docker container images in a private artifact registry.

Note

Follow the instructions below only if you’re using a private artifact registry.

Note

Unless you log out (or get logged out), you need to log in to F5 Artifact Registry only once with Helm.

Make sure your computer is connected to the public internet.
In a terminal window on your computer, make sure you’re in the F5 BIG-IP Cloud-Native Edition directory (for example, f5-big-ip-cne), which contains your F5 Artifact Registry service-account key (cne_pull_64.json).
Log in to F5 Artifact Registry with Helm:
```
cat cne_pull_64.json | helm registry login \
  --username _json_key_base64 \
  --password-stdin repo.f5.com
```
You can now use Helm commands on your computer to reference Helm charts in F5 Artifact Registry.

Note

Unless you log out (or get logged out), you need to log in to F5 Artifact Registry only once with Docker.

Make sure your computer is connected to the public internet.
In a terminal window on your computer, make sure you’re in the F5 BIG-IP Cloud-Native Edition directory (for example, f5-big-ip-cne), which contains your F5 Artifact Registry service-account key (cne_pull_64.json).
Log in to F5 Artifact Registry with Docker:
```
cat cne_pull_64.json | docker login \
  --username _json_key_base64 \
  --password-stdin repo.f5.com
```
You can now use Docker commands on your computer to reference Docker container images in F5 Artifact Registry.

In a terminal window on your computer, make sure you’re in the release-manifest directory.
Open the release manifest in a text editor.
Will you be using F5 Lifecycle Operator (not Helm) as your lifecycle-management tool?
- Yes:
  - Pull the version of the f5-lifecycle-operator Helm chart shown in the release manifest to your computer.
    
    Note
    
    To use F5 Lifecycle Operator, it’s not necessary to pull any other Helm charts.
  - Using the versions shown in the release manifest, pull all the Docker container images for F5 BIG-IP Cloud-Native Edition to your computer.
- No:
  - Using the versions shown in the release manifest, pull all the Helm charts and Docker container images for F5 BIG-IP Cloud-Native Edition to your computer.

In a terminal window on your computer, make sure you’re in the release-manifest directory.
If the private artifact registry requires authentication, log in to it with Helm and Docker.
Make sure you’re authorized to push artifacts to the private artifact registry.
Will you be using F5 Lifecycle Operator (not Helm) as your lifecycle-management tool?
- Yes:
  - Store the f5-lifecycle-operator Helm chart in the private artifact registry.
  - Store the release-manifest Helm chart in the private artifact registry.
    
    Note
    
    You pulled the release-manifest Helm chart earlier. In the F5 BIG-IP Cloud-Native Edition directory (for example, f5-big-ip-cne), look for the file named f5-bigip-k8s-manifest-<VERSION>.tgz.
  - Store all the Docker container images for F5 BIG-IP Cloud-Native Edition in the private artifact repository.
- No:
  - Store all the Helm charts and Docker container images for F5 BIG-IP Cloud-Native Edition in the private artifact repository.
Close the release manifest.