You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/11/23 22:04:07 UTC
[GitHub] [camel-k] kaczyns opened a new issue #1824: Multiple knative revisions created when integration has multiple spec.configuration items
kaczyns opened a new issue #1824:
URL: https://github.com/apache/camel-k/issues/1824
If I have an integration that contains this:
```yaml
spec:
configuration:
- type: property
value: camel.component.kafka.heartbeatIntervalMs=5000
- type: configmap
value: scm-config
- type: configmap
value: outbound-config
- type: secret
value: kafka-secrets
- type: secret
value: scm-integrations-ca-keystore
```
note that there are two configmaps and two secrets. When using the Knative profile, the Knative `Service` that is generated contains volume mounts and volumes for each configmap and secret. When the camel-k operator reconciles this integration multiple times, the order that the volumes and volume mounts appear in the `Service` is different. Knative will create a new `Revision` each time the order changes. Reconcile can happen frequently and it is not unusual to have 50-60 revisions (and therefore also pods) concurrently. The problem is worse when there are more configmaps and secrets.
----------------------------------------------------------------
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 closed issue #1824: Multiple knative revisions created when integration has multiple spec.configuration items
Posted by GitBox <gi...@apache.org>.
astefanutti closed issue #1824:
URL: https://github.com/apache/camel-k/issues/1824
----------------------------------------------------------------
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