Good afternoon, this issue regarding best approach to work with secrets in Kubernetess using Apache Camel Karavan UI
Currently we using two options: integrated Kubernetess selector in UI itself, Java-based processors
1)
2)
Both options works, but we would like to collect reasonable advice or hint for possible better approach existence.
For example, using secrets value in SetHeader component
Is there any way to use regular expressions or some other solution to avoid using separate Java-based processor that works directly with Exchange
For instance, using same pattern from components that support direct secret fetching {{secret:SECRET_NAME/KEY}}
Best regards
Describe the solution you'd like
Good afternoon, this issue regarding best approach to work with secrets in Kubernetess using Apache Camel Karavan UI
Currently we using two options: integrated Kubernetess selector in UI itself, Java-based processors 1)
2)
Both options works, but we would like to collect reasonable advice or hint for possible better approach existence.
For example, using secrets value in SetHeader component
Is there any way to use regular expressions or some other solution to avoid using separate Java-based processor that works directly with Exchange
For instance, using same pattern from components that support direct secret fetching {{secret:SECRET_NAME/KEY}}
Best regards
Variant
Web Application
Container Management (if applicable)
Kubernetes