Fix for snapshot-controller image pull error

After rebooting the active controller, the snapshot-controller pod
is no longer able to pull the image, changing to "ErrImagePull"
status.

To fix the error, the 'imagePullSecrets' field was added to the
service account of the snapshot controller from K8s 1.25 to 1.27,
specifying the secret required to authenticate to the registry
and pull the image.

Test plan:
 PASS: AIO-DX fresh install
 PASS: Reboot the active controller, checking when it returns that
       the snapshot-controller pod is running
 PASS: Reboot both controllers, checking when they return that the
       snapshot-controller pod is running

Closes-bug: 2051844

Change-Id: I68f6014898e193e561774f298c7997a3ce89a4eb
Signed-off-by: Gabriel de Araújo Cabral <gabriel.cabral@windriver.com>
This commit is contained in:
Gabriel de Araújo Cabral
2024-01-31 10:04:31 -03:00
parent e18ad6ac16
commit 504167c3ac
3 changed files with 6 additions and 0 deletions

View File

@@ -7,6 +7,8 @@ metadata:
labels:
kubernetes.io/cluster-service: "true"
addonmanager.kubernetes.io/mode: Reconcile
imagePullSecrets:
- name: registry-local-secret
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1

View File

@@ -7,6 +7,8 @@ metadata:
labels:
kubernetes.io/cluster-service: "true"
addonmanager.kubernetes.io/mode: Reconcile
imagePullSecrets:
- name: registry-local-secret
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1

View File

@@ -7,6 +7,8 @@ metadata:
labels:
kubernetes.io/cluster-service: "true"
addonmanager.kubernetes.io/mode: Reconcile
imagePullSecrets:
- name: registry-local-secret
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1