[GitHub] [camel-k] barmyard opened a new issue #2218: Scaling integrations removes Kamelet ConfigMaps

[GitBox <gi...@apache.org>]

barmyard opened a new issue #2218:
URL: https://github.com/apache/camel-k/issues/2218


   I want to pause and start Integrations by scaling the replicas to 0 and 1. When scaling integrations using `kubectl scale`, Kamelet ConfigMaps are removed. This breaks the integration.
   
   `timed-logger.yaml` Integration:
   ```yaml
   - from:
       uri: "timer:tick?period=15s"
       steps:
         - to: "kamelet:logger?message=hello"
   ```
   
   `logger` Kamelet:
   ```yaml
   apiVersion: camel.apache.org/v1alpha1
   kind: Kamelet
   metadata:
     name: logger
     labels:
       camel.apache.org/kamelet.type: "sink"
   spec:
     definition:
       title: "Logger"
       description: |-
         Logger
       required:
         - message
       properties:
         message:
           title: Message
           description: Message
           type: string
     flow:
       from:
         uri: "kamelet:source"
         steps:
           - log: "{{message}}"
   ```
   
   Steps to reproduce:
   1. `kamel run timed-logger.yaml`.
   
   ConfigMaps 
   ```
   timed-logger-kamelet-logger-flow 
   timed-logger-source-000
   timed-logger-application-properties
   ```
   2.  `kubectl scale it timed-logger --replicas 0`  
   
   ConfigMaps:
   ```
   timed-logger-source-000
   timed-logger-application-properties  
   ```
   (`timed-logger-kamelet-logger-flow ` is deleted)
   Scaling the integration to 2 results in the same behavior, the Kamelet ConfigMap is removed.
   
   3.  `kubectl scale it timed-logger --replicas 1`
   ConfigMaps:
   ```
   timed-logger-source-000
   timed-logger-application-properties  
   ```
   Log of the `camel-k-operator`:
   ```
   {"level":"info","ts":1618387208.49495,"logger":"camel-k.trait","msg":"Apply trait: init"}
   {"level":"info","ts":1618387208.4978032,"logger":"camel-k.trait","msg":"Apply trait: camel"}
   {"level":"error","ts":1618387208.5083137,"logger":"controller","msg":"Reconciler error","controller":"integration-controller","name":"timed-logger","namespace":"default","error":"error during trait customization: ConfigMap \"timed-logger-kamelet-logger-flow\" not found",
   ```
   


-- 
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.

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

[GitHub] [camel-k] nicolaferraro closed issue #2218: Scaling integrations removes Kamelet ConfigMaps

[GitBox <gi...@apache.org>]

nicolaferraro closed issue #2218:
URL: https://github.com/apache/camel-k/issues/2218


   


-- 
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.

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

[GitHub] [camel-k] astefanutti commented on issue #2218: Scaling integrations removes Kamelet ConfigMaps

[GitBox <gi...@apache.org>]

astefanutti commented on issue #2218:
URL: https://github.com/apache/camel-k/issues/2218#issuecomment-820196078


   @squakez thanks. I suspect the ConfigMap may only be added to the initialisation phase, and when the integration, in running phase, gets updated, the GC trait assumes the ConfigMap is not needed and deletes it. If that assumption is correct, the ConfigMap should also be added to the integration resources in the running phase.


-- 
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.

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

[GitHub] [camel-k] squakez commented on issue #2218: Scaling integrations removes Kamelet ConfigMaps

[GitBox <gi...@apache.org>]

squakez commented on issue #2218:
URL: https://github.com/apache/camel-k/issues/2218#issuecomment-820179529


   I'm going to have a look at this


-- 
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.

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