Christoph Deppisch
Christoph Deppisch
@oscerd so it basically follows the steps described in here, right?: https://github.com/apache/camel-k/blob/main/release.adoc
@oscerd so in this process when calling `make release-staging` the Camel K runtime staging repository is still available, right? I think this is all we need to reference the Maven...
From my understanding the maven-overlay is only used to build the Docker image. Once this is done via `make release-staging` and the reference to staging gets removed the release process...
removed the WIP marker as this is ready to be merged IMO
@squakez yes, Knative v1.5.0 uses `k8s.io/api` v0.23.5 Camel K uses v0.22.5
As this seems to be related to BSD/macOS sed and Camel K has stopped to support this please consider installing gnu-sed on your machine (see also #3372 and #3398).
IMO `--all` option is exactly that option where everything should be removed including Kamelets. The short description of `--all` option is "Do uninstall all Camel K resources". Also all CRDs...
In fact the left overs are subject to future issues because when the user performs `uninstall --all` and then does `install` on the same cluster the newly installed operator will...
If it is just 1. for the moment without any WS specific authentication mechanism I wonder if we could just use the existing Http connector. SOAP is nothing but Http...
@valdar and I talked this through and it will be the better solution to do it as suggested in this issue. I know though that it was designed in another...