docker push setup
This page describes the legacy CDM implementation, which will be deprecated in an upcoming release. We strongly recommend that you transition to the current CDM implementation as soon as possible.
In the deployment environment you’re setting up, Skaffold builds Docker images using the Docker software you’ve installed on your local computer. After it builds the images, Skaffold pushes them to a Docker registry available to your Amazon EKS cluster. With the images on the remote Docker registry, Skaffold can orchestrate the ForgeRock Identity Platform, creating containers from the Docker images.
For Skaffold to be able to push the Docker images:
Docker must be running on your local computer.
Your local computer needs credentials that let Skaffold push the images to the Docker registry available to the shared cluster.
Skaffold needs to know the location of the Docker registry.
Perform the following steps to let Skaffold to push Docker images to a registry accessible to your cluster:
If it’s not already running, start Docker on your local computer. For more information, see the Docker documentation.
Obtain your 12 digit AWS account ID. You’ll need it when you run subsequent steps in this procedure.
Log in to Amazon ECR:
$ aws ecr get-login-password | docker login --username AWS \ --password-stdin my-account-id.dkr.ecr.my-region.amazonaws.com Login Succeeded
ECR login sessions expire after 12 hours. Because of this, you’ll need to log in again whenever your login session expires .
Run the kubectx command to obtain the Kubernetes context.
Configure Skaffold with your Docker registry location and the Kubernetes context:
$ skaffold config \ set default-repo my-account-id.dkr.ecr.my-region.amazonaws.com/forgeops \ -k my-kubernetes-context set value default-repo to my-account-id.dkr.ecr.my-region.amazonaws.com/forgeops for context my-kubernetes-context
You’ve completed all the setup tasks for EKS. Now you’re ready to deploy the platform in your new cluster: