astefanutti commented on issue #1979: URL: https://github.com/apache/camel-k/issues/1979#issuecomment-805836364
Thanks @phantomjinx! Here is my current line of thought: * I'd rather avoid turning the `kamel install` options complexity into the Makefile * I'd rather propose the option for users to run `kustomize build config| kubectl apply -f -` or `kubectl -k dir`, i.e., the Makefile is optional * That means it is expected users modify the files directly, like editing the ports, commenting out patches, ... The idea is that we get back to a declarative, rather than an imperative style (with lots of options), configuration style. Specifically: * For the registry configuration, it should ideally be auto-magically be done with #1802, but in the interim, we could provide a Secret example, for users to adapt; * For the IntegrationPlatform resource created by `kamel install`, that is the recipient of most of the configuration options, we could have an IntegrationPlatform example, that would be well documented for users to adapt as it suits them. WDYT? -- 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: us...@infra.apache.org
