anerathil opened a new issue, #5060:
URL: https://github.com/apache/camel-k/issues/5060

   ### What happened?
   
   While:
   - Setting up a new K8s cluster via Kind
   - Deploying the Camel-K 2.2.0 operator (via Helm chart) with 
buildConfiguration strategy set to pod
   - Applying a integration
   
   I noticed that there were no builder pods created but the image was build 
inside the operator pod.
   
   After creating a new cluster and downgrading to operator 2.1.0 the operator 
spawned pods as expected.
   
   Attached you find the logs of the operators as well as my helmfile snipped 
to deploy the operator.
   
   
[operator_2.1.0.log](https://github.com/apache/camel-k/files/13905921/operator_2.1.0.log)
   
[operator_2.2.0.log](https://github.com/apache/camel-k/files/13905922/operator_2.2.0.log)
   
   (the error messages in the end should not matter i guess)
   
   Thanks :)
   
   ```repositories:
   - name: incubator
     url: https://charts.helm.sh/incubator
   - name: camel-k
     url: https://apache.github.io/camel-k/charts/
     
   releases:
   - name: camel-k-operator
     namespace: {{ .Values.namespaces.camelk }}
     chart: camel-k/camel-k
     version: 2.x.0 
     disableValidation: true
     labels:
       chapter: data
       package: camel-k
       component: base
     hooks:
     - events: ["preapply"]
       showlogs: true
       command: "kubectl"
       args: ["apply", "-n", "{{`{{.Values.namespaces.camelk}}`}}", "-f", 
"./templates"]
     - events: ["postuninstall"]
       showlogs: true
       command: "kubectl"
       args: ["delete", "-n", "{{`{{.Values.namespaces.camelk}}`}}", "-f", 
"./templates"]
     values:
     - operator:
         global: "true"
         resources:
           requests:
             cpu: 100m
             memory: 250Mi
       platform:
         build:
           registry:
             address: {{ env "K3d_REGISTRY_ENDPOINT" }}
             insecure: true
           buildConfiguration:
             strategy: pod
         traits:
           builder:
             tasksRequestCPU:
             - "builder:2000m"
             tasksRequestMemory:
             - "builder:2Gi"```
   
   
   ### Steps to reproduce
   
   1. Setup new cluster
   2. Deploy operator 2.2.0 via Helm chart, set strategy to pod
   3. See operator building the image in its container
   
   ### Relevant log output
   
   _No response_
   
   ### Camel K version
   
   2.2.0


-- 
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: commits-unsubscr...@camel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to