phantomjinx edited a comment on pull request #2284: URL: https://github.com/apache/camel-k/pull/2284#issuecomment-921870356
> Would it be possible to merge the `install` directory into the `config` directory, at least for the manifests / patches, to follow Kustomize conventions, and to have it working with plain Kustomize / `kubectl apply -k`. I have migrated all the patches over to the config directory but I think we should go with your original suggestion of keeping the install directory separate so as to avoid confusion with the kustomize layout. The install directory can be used to "drive" the automation of the kustomize install. > > I wonder, would you think ultimately something like `curl https://github.com/apache/camel-k/releases/download/$VERSION/installer.tar.gz | tar xvz | kubectl apply -k -` would be possible? Maybe we could produce default YAMLs as part of the release, with default configurations for Kubernetes and OpenShift, to have like `curl https://github.com/apache/camel-k/releases/download/$VERSION/openshift-install.yaml | kubectl apply -k -`. I do not think this is possible at the moment. The biggest obstacle is that the namespace of the service-account listed in the bindings is by default 'placeholder'. Therefore, I use the Makefile to call sed to change this. If this were fixed in kustomize so that 'kustomize set namespace' updated it would be worth doing. > > Once we have the structure right, I think it'll be good to go, and we'll be able to iterate subsequently on the testing and think about how to replace `kamel install`. -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
