#########################################################################################
#########################################################################################
You have seen when images are pulled from repository.
You then also understand that if an image is already present Kubernetes is not going to try to retrieve it from a repository.
(unless the imagePullPolicy parameter or the tag latest are used).
The lazy way consists into 2 steps on each Kubernetes host:
- log into Docker Hub with the command podman login
- pull all the images you need for your demos or tests with the command podman image pull
Here is list of Docker Hub images used in this lab with Trident 24.10.0:
- netapp/trident:24.10.0
- netapp/trident-operator:24.10.0
- netapp/trident-autosupport:24.10.0
- ghost:2.6-alpine
- ghost:3.13-alpine
- mysql:5.7
- busybox:1.35.0
This is more a quick workaround rather than a method you would use in production.
Have a look at the next chapter to understand how to work with secrets.
You will find in this directory a script called pull_all_images.sh that you can call to download images: This script will download the whole aforementioned list on a specific host, & uses 3 parameters:
- Hostname or host IP address
- Docker hub login
- Docker hub password
Example:
sh pull_images.sh rhel4 my_login my_password