You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current functionality of the kn-workflow CLI allows for the generation of Kubernetes resources, specifically SonataFlow CRs and a series of ConfigMap CRs, based on the application.properties file, schemas and spec folders. However, a common use case has emerged where users need to patch the generated SonataFlow CR to mount a secret into the pod, making environment variables available to the workflow's application.
To streamline this process, we propose extending the kn-workflow plugin with the ability to Generate Kubernetes Secret from secret.properties files, while ensuring proper resource ordering. We will also update the plugin documentation and will provide examples.
The text was updated successfully, but these errors were encountered:
The current functionality of the kn-workflow CLI allows for the generation of Kubernetes resources, specifically SonataFlow CRs and a series of ConfigMap CRs, based on the application.properties file, schemas and spec folders. However, a common use case has emerged where users need to patch the generated SonataFlow CR to mount a secret into the pod, making environment variables available to the workflow's application.
To streamline this process, we propose extending the kn-workflow plugin with the ability to Generate Kubernetes Secret from secret.properties files, while ensuring proper resource ordering. We will also update the plugin documentation and will provide examples.
The text was updated successfully, but these errors were encountered: