-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Helm operator does not create pods for new CR instance after I switch helm-operator from v1.33.0 to v1.34.0 #6692
Milestone
Comments
|
@lihongbj |
@acornett21 , I have tried with |
10 tasks
2 tasks
relates #6651 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 instance
kong/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
The text was updated successfully, but these errors were encountered: