Known issue for CNR where Queue-proxy image fails to pull

Products

• VMware Tanzu Application Platform

Issue/Introduction

The queue-proxy container image url is locked to initial TAP 1.4.0 url even after TAP 1.8.0 upgrade.

$ kubectl get -n knative-serving configmap/config-deployment -o yaml | grep 1.4.0

queue-sidecar-image: installpkg.azurecr.io/tanzu-application-platform-1.4.0/tap-packages@sha256:#####################

Environment

TAP 1.8.1

Cause

The bug was in the kapp rebase rules of the CNR package.

Resolution

Workaround:

Overlay rebase rule into the CNR package.

The sample:

apiVersion: v1
kind: Secret
metadata:
  name: update-queue-sidecar-overlay-secret
  namespace: tap-install
stringData:
  update-queue-sidecar-overlay-secret.yaml: |
    #@ load("@ytt:overlay", "overlay")
    
    #@overlay/match by=overlay.subset({"kind":"Config"}), expects="1+"
    ---
    rebaseRules:
      #@overlay/append
      - path: [data, queue-sidecar-image]
        type: copy
        sources: [new, existing]
        resourceMatchers:
          - kindNamespaceNameMatcher: {kind: ConfigMap, namespace: knative-serving, name: config-deployment}

 

The long term resolution:

The fix will come into TAP v1.12.1.