Deploying images from a private container registry¶

You can configure your Knative cluster to deploy images from a private registry across multiple Services and Revisions. To do this, you must create a list of Kubernetes secrets (imagePullSecrets) by using your registry credentials. You must then add those secrets to the default service account for all Services, or the Revision template for a single Service.

Prerequisites¶

You must have a Kubernetes cluster with Knative Serving installed.
You must have access to credentials for the private container registry where your container images are stored.

Procedure¶

Create a imagePullSecrets object that contains your credentials as a list of secrets:
```
kubectl create secret docker-registry <registry-credential-secrets> \
  --docker-server=<private-registry-url> \
  --docker-email=<private-registry-email> \
  --docker-username=<private-registry-user> \
  --docker-password=<private-registry-password>
```
Where:
- <registry-credential-secrets> is the name that you want to use for your secrets (the imagePullSecrets object). For example, container-registry.
- <private-registry-url> is the URL of the private registry where your container images are stored. Examples include Google Container Registry or DockerHub.
- <private-registry-email> is the email address that is associated with the private registry.
- <private-registry-user> is the username that you use to access the private container registry.
- <private-registry-password> is the password that you use to access the private container registry.
Example:
```
kubectl create secret docker-registry container-registry \
  --docker-server=https://gcr.io/ \
  --docker-email=my-account-email@address.com \
  --docker-username=my-grc-username \
  --docker-password=my-gcr-password
```
Optional. After you have created the imagePullSecrets object, you can view the secrets by running:
```
kubectl get secret <registry-credential-secrets> -o=yaml
```
Optional. Add the imagePullSecrets object to the default service account in the default namespace.

Note

By default, the default service account in each of the namespaces of your Knative cluster are used by your Revisions, unless the serviceAccountName is specified.

For example, if have you named your secrets container-registry, you can run the following command to modify the default service account:
```
kubectl patch serviceaccount default -p "{\"imagePullSecrets\": [{\"name\": \"container-registry\"}]}"
```
New pods that are created in the default namespace now include your credentials and have access to your container images in the private registry.

Optional. Add the imagePullSecrets object to a Service:

apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  name: hello
spec:
  template:
    spec:
      imagePullSecrets:
      - name: <secret-name>
      containers:
        - image: ghcr.io/knative/helloworld-go:latest
          ports:
            - containerPort: 8080
          env:
            - name: TARGET
              value: "World"