Mohid-A opened a new issue, #3441:
URL: https://github.com/apache/camel-k/issues/3441

   Hi Community,
   
   We are running into an issue when the camel-k operator restarts when we have 
more than four integrations running on OCP(version mentioned below). Upon 
restart, the operator keeps on reconciling the integrations continuously which 
causes CPU spikes on the master node, also resulting in the latency on the 
kube-api server. The logs for the issue is mentioned below,
   
   **VERSION**
   
   Camel-k-operator 1.9.1
   Camel K Client 1.9.1
   OCP 4.9.37Using Kubernetes 1.22
   
   **Command to produce the Issue**
   
    kamel --kube-config=$QA_KUBECONFIG run $APP(integration file variable) 
--trait container.enabled=$ENABLED --trait container.request-cpu=$REQUESTCPU 
--trait container.request-memory=$REQUESTMEMORY --trait 
container.limit-cpu=$LIMITCPU --trait container.limit-memory=$LIMITMEMORY 
--trait jvm.options=-Doracle.jdbc.timezoneAsRegion=false --pod-template $PVC2 
--config secret:$SECRET --config configmap:$CONFIGMAP -t logging.level=DEBUG
   
   
   **Error Log**
   
   
   ```
   
{"level":"info","ts":1657633698.0446534,"logger":"camel-k.controller.integration","msg":"Reconciling
 
Integration","request-namespace":"esb-jpoller-qa","request-name":"send-email-notification"}
   
{"level":"info","ts":1657633698.0447812,"logger":"camel-k.controller.integration","msg":"Invoking
 action 
monitor","request-namespace":"esb-jpoller-qa","request-name":"send-email-notification","api-version":"camel.apache.org/v1","kind":"Integration","ns":"esb-jpoller-qa","name":"send-email-notification"}
   
{"level":"info","ts":1657633698.3031335,"logger":"camel-k.controller.integration","msg":"Reconciling
 
Integration","request-namespace":"esb-jpoller-qa","request-name":"appointments3plcn-wh42"}
   
{"level":"info","ts":1657633698.3032014,"logger":"camel-k.controller.integration","msg":"Invoking
 action 
monitor","request-namespace":"esb-jpoller-qa","request-name":"appointments3plcn-wh42","api-version":"camel.apache.org/v1","kind":"Integration","ns":"esb-jpoller-qa","name":"appointments3plcn-wh42"}
   
{"level":"info","ts":1657633698.5536115,"logger":"camel-k.controller.integration","msg":"Reconciling
 
Integration","request-namespace":"esb-jpoller-qa","request-name":"send-email-notification"}
   
{"level":"info","ts":1657633698.5536752,"logger":"camel-k.controller.integration","msg":"Invoking
 action 
monitor","request-namespace":"esb-jpoller-qa","request-name":"send-email-notification","api-version":"camel.apache.org/v1","kind":"Integration","ns":"esb-jpoller-qa","name":"send-email-notification"}
   
{"level":"info","ts":1657633698.9342558,"logger":"camel-k.controller.integration","msg":"Reconciling
 
Integration","request-namespace":"esb-jpoller-qa","request-name":"appointments3plcn-wh42"}
   
{"level":"info","ts":1657633698.9343414,"logger":"camel-k.controller.integration","msg":"Invoking
 action 
monitor","request-namespace":"esb-jpoller-qa","request-name":"appointments3plcn-wh42","api-version":"camel.apache.org/v1","kind":"Integration","ns":"esb-jpoller-qa","name":"appointments3plcn-wh42"}
   
{"level":"info","ts":1657633699.1299353,"logger":"camel-k.controller.integration","msg":"Reconciling
 
Integration","request-namespace":"esb-jpoller-qa","request-name":"appointments3plcn-wh42"}
   
{"level":"info","ts":1657633699.1300168,"logger":"camel-k.controller.integration","msg":"Invoking
 action 
monitor","request-namespace":"esb-jpoller-qa","request-name":"appointments3plcn-wh42","api-version":"camel.apache.org/v1","kind":"Integration","ns":"esb-jpoller-qa","name":"appointments3plcn-wh42"}
   ```
   **Expected Behavior**
   
   We want the operator to be stable upon restart, as restarting has an impact 
on the platform and other workloads.
   
   Thanks


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to