Update your Edge private registries
You can update the location or credentials of your Edge site private registry to align with your organization's policies. This maintains secure and consistent access to your private registry.
Edge sites on bundled k3s
Follow the steps below to update your private container image registry on an Edge site installed on bundled k3s.
Prerequisites
- You installed your Edge site on bundled k3s with a private container image registry.
- You have access to your registry.
Steps
- If you need to update the location of the registry, run the following command, replacing
<registry-url>with the new registry URL:Copysudo ./edgecli update --set global.collibra.imageRegistry=<registry-url> - Use the following command to locate the registries.yaml file: Copy
vi /etc/rancher/k3s/registries.yamlShow me an example of the registries.yaml fileBelow is an example of a registries.yaml file.
Copymirrors:
docker.io:
endpoint:
- https://edge-docker-delivery.repository.collibra.io
rewrite: {}
edge-docker-delivery.repository.collibra.io:
endpoint:
- https://edge-docker-delivery.repository.collibra.io
rewrite: {}
gcr.io:
endpoint:
- https://edge-docker-delivery.repository.collibra.io
rewrite: {}
quay.io:
endpoint:
- https://edge-docker-delivery.repository.collibra.io
rewrite: {}
configs:
edge-docker-delivery.repository.collibra.io:
auth:
username: newusername1
password: newpassword12 - Update the registry URL or credentials in the registries.yaml file.
- Save the file.
- Restart k3s:
Copy
sudo systemctl restart k3s
Edge site on a managed Kubernetes cluster
Follow the steps below to update your private container image registry on an Edge site installed on a managed Kubernetes cluster.
Prerequisites
- You installed your Edge site on a managed Kubernetes cluster with a private container image registry.
- You have access to the Kubernetes cluster via kubctl.
- You have access to the registry.
Steps
- Run the following command from the Edge CLI if you want to update the location of your private container image registry:
Copy
sudo ./edgecli update --set global.collibra.imageRegistry=<registry-url> - Run the following command from your terminal to open your registries file. Update the credential or URL of your private container image registry in this file.Copy
vi /etc/rancher/k3s/registries.yaml
Prerequisites
- You installed your Edge site on a managed Kubernetes cluster with a private helm image registry.
- You have access to the Kubernetes cluster via kubctl.
- You have access to the registry.
Steps
Use the following commands to update your registry URL or credentials in the collibra-edge-repo-creds secret. These commands can be used for Edge sites installed on bundled k3s or a managed Kubernetes cluster.
- Run this command to specify the new credentials: Copy
kubectl create secret generic collibra-edge-repo-creds \
--from-literal=url=<helm_repo_url> \
--from-literal=username=<username> \
--from-literal=password=<password> \
--dry-run=client -o yaml | kubectl apply -n <your_namespace> -f - -
Run this command to apply your changes:
Copy./edgecli update --set global.helmRepository=<helm_repo_url>
kubectl create secret generic collibra-edge-repo-creds \
--from-literal=url=https://repository.collibra.io/artifactory/edge-helm-platinum \
--from-literal=username=username12 \
--from-literal=password=password123 \
--dry-run=client -o yaml | kubectl apply -n collibra-edge -f -
./edgecli update --set global.helmRepository=https://repository.collibra.io/artifactory/edge-helm-platinum
Whats next
- Create an Edge site connection.
- Create an Edge site capability.