Before you begin¶
Introduction¶
The following instructions describe how to set important environment variables and log in to the appropriate artifact registry.
Set the release-manifest version¶
Set the
CNE_RELEASE_MANIFEST_VERSIONenvironment variable to the F5 BIG-IP Cloud-Native Edition version.Example
export CNE_RELEASE_MANIFEST_VERSION=2.4.0
Set the repository address and log in to the appropriate artifact registry with Helm¶
Are you using a private artifact registry to store the F5 BIG-IP Cloud-Native Edition Helm charts and Docker container images?
Yes:
Set the
CNE_REPOenvironment variable to the address of the F5 BIG-IP Cloud-Native Edition repository in your private artifact registry.Example
export CNE_REPO=registry.company.com/f5-big-ip-cne
Log in to your private artifact registry with Helm.
Skip the next task (Log in to F5 Artifact Registry with Helm).
No:
Set the
CNE_REPOenvironment variable to the address of F5 Artifact Registry:export CNE_REPO=repo.f5.com
Note
There is only one repository in F5 Artifact Registry, so the address of the registry is also the address of the repository.
Log in to F5 Artifact Registry with Helm¶
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.
Next steps¶
To continue installing, go to Install the F5 CRDs and the CNE core using Helm.