Tanzu Package Repository Update Not Reflected in Existing Deployments

Products

• VMware Tanzu Kubernetes Grid

Issue/Introduction

Tanzu package repository update is not being taken any effect in the already running deployments. 

You can see that the package repository is updated correctly and so do the applications, however when describing a pod or a deployment you will see that the images are pointing to the old Tanzu package repository url.

 

Cause

This issue is caused by a caching mechanism within kapp-controller. When the Tanzu package repository url is updated, the image references may not update if the image’s SHA remains unchanged between the old and new Tanzu package repository image.

Resolution

To resolve this issue, restart the kapp-controller deployment to clear any cached references to the Tanzu package repository url.

Steps:

1. Restart the kapp-controller deployment: kubectl rollout restart -n <kapp-controller-namespace> deploy kapp-controller
2. Verify that the kapp-controller deployment has restarted successfully: kubectl get pods -n <namespace> (Ensure the kapp-controller pod is in a Running state.)
3. Confirm that new pods pull images from the correct Tanzu package repository url: kubectl describe pod <pod-name> -n <namespace> | grep Image