Hot-Patch an Arbitrary Image in Your Deployment¶
This section will guide you through setting custom container images for the components of Rok and Rok Registry.
This is an advanced guide that you should not follow, unless Arrikto has
instructed you to do so. Arrikto should first provide you with a custom
container image and its
<TAG>, for each component that you are going to
What You'll Need¶
- A configured management environment.
- Your clone of the Arrikto GitOps repository.
- An existing Rok deployment.
- A custom container image provided by Arrikto, for each component that you are going to hot-patch.
- A mirror of those images in your internal registry.
Repeat the procedure below for every Rok and Rok Registry component that you wish to hot-patch. Choose the corresponding tab at the beginning of each iteration.
Go to your GitOps repository inside your
root@rok-tools:~# cd ~/ops/deployments
Edit the corresponding YAML manifests:
If the lines in the snippet already exist in the
kustomization.yamlchange them to match the snippet instead of appending new ones.
Optionally, you can push your local changes to a remote of your choice.
Apply the kustomization:
Repeat the procedure below for every Rok and Rok Registry component whose image you wish to verify. Choose the corresponding tab at the beginning of each iteration.
Extract the container image used in the corresponding Kubernetes resource:
Verify that the container image is the correct one:
You have successfully set custom images for Rok and Rok Registry components.