Closed lihongbj closed 3 weeks ago
@lihongbj 1.34.0
's release did not complete fully. Can you try updating to 1.34.1
to see if this resolves your issue?
@acornett21 , I have tried with v1.34.1
and the issue is still reproduced with same symptom.
relates #6651
Bug Report
What did you do?
Deploying helm chart CR failed with helm-operator v1.34.0, that CR's pods did not get created at all.
I defined a CRD
kong
for helm chart Kong, and use helm operator to deploy it, and awatches.yaml
is also defined to watch kong. When deploying, first the helm operator pod is deployed, and then a new CR instancekong/gateway
is created so kong CR instance pods should be created accordingly. In helm operator with v1.33.0, those CR pods are created as expected while in new v1.34.0, those CR pods are NOT created at all. What's more, no new text are logged in helm operator pod log since new CR instance is created.What did you expect to see?
Those CR's pods are created and running as in helm-operator v1.33.0, and helm operator pod log echo this like below:
kong CR:
pod list:
helm-operator pod log:
What did you see instead? Under which circumstances?
No CR pods are created and no new log are dump in helm operator pod log.
kong CR:
pod list:
helm-operator pod log:
Environment
Operator type:
Kubernetes cluster type:
$ operator-sdk version
$ go version
(if language is Go) go: 1.21.5.$ kubectl version
Possible Solution
Additional context