squakez commented on PR #4190: URL: https://github.com/apache/camel-k/pull/4190#issuecomment-1491423980
@mertdotcc yeah, the main problem is that the E2E are thought to be run in a local cluster. Basically the idea is that they take care of installing everything needed by the test using a local registry. It would be possible to tweak them in order to run remotely like you're trying to do, however, I think that it is not a worth to go in that direction. If you try to do the local development and test using Minikube or Kind, it would be much easier. IMO, you should try to run a Minikube locally and see how compares the development experience. Basically it turns out in the following steps: ``` minikube start minikube addons enable registry // only the first time after you install minikube eval $(minikube -p minikube docker-env) // only once when you start a command shell make images // will push your local operator where it is expected to be make test-common ``` If you're planning to work on Camel K, I think in the long run you'll see a lot of benefits compared to deploying directly to a remote cluster. Feel free to reach out for any more advice. -- 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
