expand/awx-on-k3s
1
0
Fork 0
mirror of https://github.com/Expand-sys/awx-on-k3s synced 2025-12-16 05:52:15 +11:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request #63 from vrubiolo/vrubiolo

Browse source 
Improve documentation for using private registries
This commit is contained in:
kurokobo 2022-04-26 23:21:23 +09:00 committed by GitHub
commit 772156bd87
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
registry/README.md
View file

@ -207,10 +207,10 @@ sudo systemctl restart k3s
If this is successfully applied, you can check the applied configuration in the `config.registry` section of the following command.
```bash
sudo /usr/local/bin/crictl info
sudo /usr/local/bin/k3s crictl info
# With jq
sudo /usr/local/bin/crictl info | jq .config.registry
sudo /usr/local/bin/k3s crictl info | jq .config.registry
```
If you want Kubernetes to be able to pull images directly from this private registry, alternatively you can also manually create `imagePullSecrets` for the Pod instead of writing your credentials in `auth` in `registries.yaml`. [Another guide about rate limiting on Docker Hub](../tips/dockerhub-rate-limit.md) explains how to use `ImagePullSecrets`.