-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRDs causes the whole K8s cluster not to work properly #906
Comments
hi, do you install |
yeah sure。 |
I used |
I didn't reproduce this with kind 1.22.0 and eks 1.22.6.
|
After careful investigation, some resources are not installed properly during the installation of |
We encounter the same issue and resolve it with AWS support. I think it is not related to cert manger. |
k8s version: eks 1.22.9/k8s 1.22.9
harbor-operator crd version: 1.2.0
Creating a resource with any harbor-operator crd(eg: chartmuseums.goharbor.io) will result in a large number of internal error logs in the
kube-crontroller-manager
component log. The resources of the entire cluster cannot be deleted normally. eg: create a deployment resource, and then delete it, and you will find that the associated replicas and pod cannot be deleted.like this:
$ kubectl create deployment myapp --image nginx:alpine deployment.apps/myapp created $ kubectl get po NAME READY STATUS RESTARTS AGE myapp-7c5c94c888-wwz4k 1/1 Running 0 6s $ kubectl delete deploy myapp deployment.apps "myapp" deleted $ kubectl get po NAME READY STATUS RESTARTS AGE myapp-7c5c94c888-wwz4k 1/1 Running 0 14s $ kubectl get rs NAME DESIRED CURRENT READY AGE myapp-7c5c94c888 1 1 1 14s
kube-controller-manager logs:
Another thing, I found that there are a lot of key-value
caBundle: Cg==
in the crd resource. After the CRD resource is created, this value is not replaced with something likecaBundle: "Ci0tLS0tQk... < base64-encoded PEM bundle > .tLS0K"
. I don't know if it has any effect on this.reproduce:
chartmuseums.goharbor.io
kubectl create deployment myapp
kubectl delete deployment myapp
kubectl get deploy,replicas,pod |grep myapp
Internal error occurred
The text was updated successfully, but these errors were encountered: