Unusually High Core Usage with Upstream Docker Image for helm operator. #6679
Labels
language/helm
Issue is related to a Helm operator project
triage/support
Indicates an issue that is a support question.
Milestone
Bug Report
What did you do?
I am creating an helm based operator for Redhat Openshift. Earlier I was using the downstream image i.e
![image](https://private-user-images.githubusercontent.com/37516416/304837475-3a0233da-cf63-40fe-b5e5-13e951f94671.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk3OTc5NjMsIm5iZiI6MTcxOTc5NzY2MywicGF0aCI6Ii8zNzUxNjQxNi8zMDQ4Mzc0NzUtM2EwMjMzZGEtY2Y2My00MGZlLWI1ZTUtMTNlOTUxZjk0NjcxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzAxVDAxMzQyM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNiMzM0YTg4OGE1NTBkYTQ5MzI5ZGI0MGEzMjhjZjVkMjBiZjQ1NDk3ZmZlMGY4Nzg2MDg1MTIxNDdhOGVmYTAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.rFeB6blQqw47Wxqrfiu9IA98_M62F8nB_JIIcdSulyQ)
registry.redhat.io/openshift4/ose-helm-operator:latest
as my base image and myoperator-controller-manager
deployment was taking around 0.06-0.08 cores,Then I updated my base image to the upstream image i.e
![image](https://private-user-images.githubusercontent.com/37516416/304837569-32ab315c-92d5-4cbb-b876-dbdd876b6a3e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk3OTc5NjMsIm5iZiI6MTcxOTc5NzY2MywicGF0aCI6Ii8zNzUxNjQxNi8zMDQ4Mzc1NjktMzJhYjMxNWMtOTJkNS00Y2JiLWI4NzYtZGJkZDg3NmI2YTNlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzAxVDAxMzQyM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTgxNTc3NzRlOTUxMjQ2YmM2YWNiY2ZiMTc2ZGUyNGFiZGY2ODMzMzdmY2RiZjA3Y2IwMTQxMDgyYjRhZTlhOGUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.RUV3ELt-arVUcHmpr0rtytYIAtJlJfSkFlWM15VfbRs)
quay.io/operator-framework/helm-operator:latest
and the core usage for the sameoperator-controller-manager
increased very much to like 0.8-0.9 cores.What did you expect to see?
Usual core usage around 0.05-0.06
What did you see instead? Under which circumstances?
Very high core usage around 1
Environment
Operator type:
/language helm
Kubernetes cluster type:
OpenShift v4.13.4
$ operator-sdk version
$ go version
(if language is Go)$ kubectl version
Possible Solution
Additional context
The text was updated successfully, but these errors were encountered: