Custom Docker Registry - Containers - Confluent Community = 40rem)" rel="stylesheet" data-target="discourse-ai_desktop" /> = 40rem)" rel="stylesheet" data-target="discourse-events_desktop" /> = 40rem)" rel="stylesheet" data-target="discourse-reactions_desktop" /> = 40rem)" rel="stylesheet" data-target="poll_desktop" /> = 40rem)" rel="stylesheet" data-target="desktop_theme" data-theme-id="4" data-theme-name="discourse gifs"/> Custom Docker Registry Ops Containers pg74 22 March 2024 20:31 1 Despite my efforts to update the CRD for kafkas.platform.confluent.io to utilize images from my Custom Docker Registry, and ensuring that the Kubernetes StatefulSet for Kafka was also updated accordingly to fetch the image from the custom Docker registry, I am encountering a persistent issue where the pods continue to use the outdated image. Strikingly, this anomaly appears to be confined solely to the Kafka StatefulSet. I kindly request guidance on resolving this perplexing matter. Confluentfor Kubernetes (CFK) - Operator 0.921.2 cp-server:7.6.0 confluent-init-container:2.8.0 My Kubernetes cluster is RKE2 version v1.24.9+rke2r1 mmuehlbeyer 19 April 2024 10:02 2 did you try to change or update image pull policy? spec: image: pullPolicy: Always see https://docs.confluent.io/operator/current/co-api.html#tag/Kafka for reference