knative
/
docs
mirror of https://github.com/knative/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Delete duplicate deploying-from-private-registry.md file (#4146) 

* Delete deploying-from-private-registry.md

* Add back a change from the deleted version of the file

* Fix broken link
This commit is contained in:
Samia Nneji 2021-09-07 17:03:18 +01:00 committed by GitHub
parent 58b2667e8b
commit 18e15fc07c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 2 additions and 89 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/admin/install/operator/configuring-serving-cr.md
View File

@ -112,7 +112,7 @@ location. This section is only needed when the registry images do not match the
- `imagePullSecrets`: a list of Secret names used when pulling Knative container images. The Secrets - `imagePullSecrets`: a list of Secret names used when pulling Knative container images. The Secrets
must be created in the same namespace as the Knative Serving Deployments. See [deploying images must be created in the same namespace as the Knative Serving Deployments. See [deploying images
from a private container registry](../../../serving/deploying-from-private-registry.md) for configuration details. from a private container registry](../../../developer/serving/deploying-from-private-registry.md) for configuration details.
### Download images in a predefined format without secrets: ### Download images in a predefined format without secrets:

2
docs/developer/serving/deploying-from-private-registry.md
View File

@ -44,7 +44,7 @@ To configure using a private container registry, you must:
Example: Example:
```bash ```bash
kubectl create secret container-registry \ kubectl create secret docker-registry container-registry \
--docker-server=https://gcr.io/ \ --docker-server=https://gcr.io/ \
--docker-email=my-account-email@address.com \ --docker-email=my-account-email@address.com \
--docker-username=my-grc-username \ --docker-username=my-grc-username \

87
docs/serving/deploying-from-private-registry.md
View File

@ -1,87 +0,0 @@
# Deploying images from a private container registry
Learn how to configure your Knative cluster to deploy images from a private
container registry.
To share access to your private container images across multiple services and
revisions, you create a list of Kubernetes secrets
([`imagePullSecrets`](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#pod-v1-core))
using your registry credentials, add that `imagePullSecrets` to your default
[service account](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/),
and then deploy those configurations to your Knative cluster.
## Before you begin
You need:
- A Kubernetes cluster with [Knative Serving installed](../admin/install/serving/install-serving-with-yaml.md).
- The credentials to the private container registry where your container images are stored.
## Configuring your credentials in Knative
1. Create a `imagePullSecrets` that contains your credentials as a list of secrets:
```bash
kubectl create secret docker-registry [REGISTRY-CRED-SECRETS] \
--docker-server=[PRIVATE_REGISTRY_SERVER_URL] \
--docker-email=[PRIVATE_REGISTRY_EMAIL] \
--docker-username=[PRIVATE_REGISTRY_USER] \
--docker-password=[PRIVATE_REGISTRY_PASSWORD]
```
Where
- `[REGISTRY-CRED-SECRETS]` is the name that you want for your secrets
(`imagePullSecrets` object). For example, `container-registry`.
- `[PRIVATE_REGISTRY_SERVER_URL]` is the URL to the private
registry where your container images are stored.
Examples:
- Google Container Registry: [https://gcr.io/](https://gcr.io/)
- DockerHub [https://docker.io/](https://docker.io/)
* `[PRIVATE_REGISTRY_EMAIL]` is your 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:
```bash
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
```
Tip: After creating the `imagePullSecrets`, you can view those secret's by running:
```bash
kubectl get secret [REGISTRY-CRED-SECRETS] --output=yaml
```
1. Add the `imagePullSecrets` to your `default` service account in the
`default` namespace.
Note: By default, the `default` service account in each of the
[namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/)
of your Knative cluster are use by your revisions unless [`serviceAccountName`](https://github.com/knative/specs/blob/main/specs/serving/knative-api-specification-1.0.md#revision-2) is specified.
Run the following command to modify your `default` service account, assuming
you named your secrets `container-registry`:
```bash
kubectl patch serviceaccount default -p "{\"imagePullSecrets\": [{\"name\": \"container-registry\"}]}"
```
Now, all the new pods that are created in the `default` namespace will include
your credentials and have access to your container images in the private registry.
## What's next
[Learn how to create a Knative service](getting-started-knative-app.md).