create a ServiceAccount after the CRD applied the ServiceAccount is not updating by the operator about registry-creds HOT 3 CLOSED

I came here to report I think the same issue, although my report is shaped slightly differently.

I create an NS "nginx-ingress" and install the ingress controller via Helm chart, immediately after setting up my ClusterPullSecret resource. I follow the same step kubectl get -n default serviceaccounts default -oyaml and see an imagePullSecrets ref there, - name: dockerhub-registrycreds just as expected, but the default service account in my newly created ns nginx-ingress is missing the imagePullSecret ref.

Deleting and recreating the ClusterPullSecret resolves it. So basically the same behavior issue as reported above by @developer-guy – new namespaces get the secret copied successfully, but the imagePullSecret reference is not added to the service accounts. My cluster is a Kind 1.19.1 on MacOS, with Docker Desktop 2.5.0.0 backing the cluster.

from registry-creds.

hello @kingdonb, we fixed this problem at PR #14, we are waiting for this PR to be approved by Alex, then we will catch the ServiceAccount creation event and update it accordingly.

from registry-creds.

@alexellis I think we can close this issue.

from registry-creds.