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


   Following on from #1743 ....
   
   * Refactor and remove any duplication between the `deploy` and `config` 
directories;
   * The `config` directory should now become the source of truth for the 
artifacts, where applicable, retargetting the kamel CLI accordingly;
   * Make clear in README that the bundle directory should be generated on an 
as-needed basis rather than being checked-in (the CSV manifest resources are 
checked-in);
   * Start to offer camel-k as an install with kustomize rather than needing to 
download the `kamel cli`, allowing install with standard tools;
     - This will require consideration of different production setups, 
tailoring the `config` directory to support patches for different use-cases, 
eg. including addons, installing on different types of cluster;
     - Need to gauge any comparable loss of flexibility as compared to the 
kamel cli;


----------------------------------------------------------------
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:
[email protected]


Reply via email to