#We ve never had to login to docker
dreamy pecan
You'll want to add the Trident image and then Trident Autosupport image. The Trident Operator will pull those two images from the docker registry when installing Trident.
For a Trident Operator based install you'll want to specify that following:
spec.autosupportImage: "yourRegistry.io/trident-autosupport:22.10
spec.tridentImage: "yourRegistry.io/trident:21.10.1
You can also run the tridentctl images command to see the images needed for a particular version of Trident. That information can also be found on the Requirements section in the Trident documentation. https://docs.netapp.com/us-en/trident-2110/trident-get-started/requirements.html#storage-system-configuration
If you want to also put the CSI sidecar images in your private registry then you'd want to modify the Operator with:
spec.autosupportImage: "yourRegistry.io/trident-autosupport:22.10
spec.tridentImage: "yourRegistry.io/trident:21.10.1
spec.imageRegistry: "yourRegistry.io" <-- CSI sidecar images go here
mighty charm
Thanks @dreamy pecan So when upgrading from 20.10.1 to 21.10.1, the docs have us create the crd with
kubectl create -f trident-installer-21.10.1/deploy/crds/trident.netapp.io_tridentorchestrators_crd_post1.16.yaml- Delete the old deployed operator:
kubectl delete -f trident-installer-20.10.1/deploy/bundle.yaml -n trident - Create the new version with
kubectl create -f trident-installer-21.10.1/deploy/bundle.yaml -n trident
Little confused on where we'd actually specify those settings. It would be nice if there was a global parameter for setting an internal registry instead of declaring it for each image.
dreamy pecan
@mighty charm, I agree with that but different customers set up their private registries differently. Many of them are restricted by corp processes so we had to make it more flexible than you would initially think is needed.
rough swallow
In addition and hopefully to correlate from above, does this help?
You can setup a private registry and download the Trident binaries one time into your own registry.
Once completed, follow the steps to customize the orchestrator yamll to point to their local registry, as described here:
https://docs.netapp.com/us-en/trident/trident-get-started/kubernetes-deploy.html#offline-deployment
"If you are deploying Astra Trident by using the Trident operator, ensure that the orchestrator CR includes tridentImage and autosupportImage in the installation parameters."
https://docs.netapp.com/us-en/trident/trident-get-started/kubernetes-customize-deploy.html
mighty charm
Thanks, @dreamy pecan and @rough swallow Reading the Offline Deployment section, It looks like there is an attribute that can be applied to the TridentOrchestrator spec.imageRegistry to point to an internal registry. Looks like I'm back to testing this again. Thanks all.