wmedvede opened a new issue, #2938:
URL: https://github.com/apache/incubator-kie-tools/issues/2938
When the user defines a SonataFlowPlatform like this:
```
apiVersion: sonataflow.org/v1alpha08
kind: SonataFlowPlatform
metadata:
name: sonataflow-platform
spec:
services:
dataIndex:
enabled: true
podTemplate:
containers:
- name: data-index-service
env:
- name: QUARKUS_HTTP_CORS
value: "true"
- name: QUARKUS_HTTP_CORS_ORIGINS
value:
https://data-index-route-tls-usecase3-platform-persistence-oc.apps-crc.testing
replicas: 1
jobService:
enabled: true
```
The expectation is that user provided env configuration:
```
env:
- name: QUARKUS_HTTP_CORS
value: "true"
- name: QUARKUS_HTTP_CORS_ORIGINS
value:
https://data-index-route-tls-usecase3-platform-persistence-oc.apps-crc.testing
```
Should added to the corresponding Deployment/Pod. This facilitates potential
fine-tunings of any of these services. However, it is not.
We must add that ability, at the same time of evaluating how to deal with
potential clashing between user provided and operator managed configurations.
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
