mertdotcc commented on PR #4190: URL: https://github.com/apache/camel-k/pull/4190#issuecomment-1491561559
My reasons for choosing a remote cluster over minikube were: 1. I already have a personal cluster with enough nodes and necessary resources dedicated to this type of stuff, testing, building, etc. 2. I am using an M1 Mac with 16GB of RAM and without having the Docker Engine or the minikube running, I am already at around 80% memory utilization rate. 😕 3. In the past (this was over 2 years ago) I experienced some different behaviours when I used to deploy exact same manifests in an actual cluster vs a minikube cluster. Since that day, I am a bit hesitant to work with minikube. (This might very well be due to my lack of experience at that time, or maybe minikube came a long way). I feel like when I test full-fledged operations with `prometheus` enabled, `jaeger` enabled, doing smoke tests, and sending 100000 requests using `iter8` or something, minikube won't "hold up" and I would rather work in an actual cluster. That being said though, I will follow the steps you mentioned for minikube and switch over my workflow there. Do you have any idea what might have been wrong with my cluster though? Even if you have minor suspicions I would like to follow&explore them in my free time. Thanks. -- 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
