harbor-operator: Too many replica set are created for registry-ctl component

Run make sample

Then check the resource, you’ll find more than one registry-ctl replica sets that with 0, 0.

replicaset.apps/sample-harbor-registryctl-589b8bb8df   1         1         1       2m16s
replicaset.apps/sample-harbor-registryctl-5bbf7d4889   0         0         0       2m36s
replicaset.apps/sample-harbor-registryctl-644bd8fdbf   0         0         0       2m47s
replicaset.apps/sample-harbor-registryctl-644d9549b6   0         0         0       2m50s
replicaset.apps/sample-harbor-registryctl-687bbd59cd   0         0         0       2m34s
replicaset.apps/sample-harbor-registryctl-6988fbbfbd   0         0         0       2m42s
replicaset.apps/sample-harbor-registryctl-7464d974bb   0         0         0       2m45s
replicaset.apps/sample-harbor-registryctl-74c6d4f8cc   0         0         0       2m35s
replicaset.apps/sample-harbor-registryctl-7569fb84f4   0         0         0       2m52s
replicaset.apps/sample-harbor-registryctl-79cc6ccbf    0         0         0       2m46s
replicaset.apps/sample-harbor-registryctl-c58b8b4d8    0         0         0       2m56s

Deployment is not ready:

NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/sample-harbor-registryctl   0/1     1            0           2d3h

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 17

Commits related to this issue

Fix(reconciliation) Rework reconciliation loop. Close #131. * Use server side apply instead of client side apply (https://kubernetes.io/docs/reference/using-api/server-side-apply/) Remove pkg/resou... — committed to sguyennet/harbor-operator by sguyennet 4 years ago
Fix(reconciliation) Rework reconciliation loop. Close #131. * Use server side apply instead of client side apply (https://kubernetes.io/docs/reference/using-api/server-side-apply/) Remove pkg/resou... — committed to sguyennet/harbor-operator by sguyennet 4 years ago
Fix(reconciliation) Rework reconciliation loop. Close #131. * Use server side apply instead of client side apply (https://kubernetes.io/docs/reference/using-api/server-side-apply/) Remove pkg/resou... — committed to sguyennet/harbor-operator by sguyennet 4 years ago
Fix(reconciliation) Rework reconciliation loop. Close #131. * Use server side apply instead of client side apply (https://kubernetes.io/docs/reference/using-api/server-side-apply/) Remove pkg/resou... — committed to sguyennet/harbor-operator by sguyennet 4 years ago
Fix(reconciliation) Rework reconciliation loop. Close #131. * Use server side apply instead of client side apply (https://kubernetes.io/docs/reference/using-api/server-side-apply/) Remove pkg/resou... — committed to sguyennet/harbor-operator by sguyennet 4 years ago
Fix(reconciliation) Rework reconciliation loop. Close #131. * Use server side apply instead of client side apply (https://kubernetes.io/docs/reference/using-api/server-side-apply/) Remove pkg/resou... — committed to sguyennet/harbor-operator by sguyennet 4 years ago
Merge pull request #339 from sguyennet/dev/fix-registryctl Rework reconcilation loop. Fix #131. — committed to goharbor/harbor-operator by steven-zou 3 years ago

Most upvoted comments

Hi Steven,

We identified the root cause of the issue. The operator is watching the secret of the registry internal certificate. When the secret is created, it is created empty and then populated with the certificate. For the operator the secret exist, therefore he deploy the registry and the registryctl. When the certificate is inserted in the secret the operator detect the modification and change the resource version of the registry, which trigger a redeploy of the registryctl because the checksum of the registry have changed.

I will modify the code of the operator in charge of checking if the secret exist or not.

sguyennet on Nov 26, 2020