GitHub user potiuk added a comment to the discussion: Kuberentes integration settings/commands for Breeze environment?
> Increased RAM to maximum (8GB on the machine) and now only API server failed > on startup. Looks like a common issue for 3.0 deployment: Look at k8s error logs and why it does not start. Generally when pod fails to start you can find out in k8s logs why. Without it, it's pure guess. Maybe there is some specific WSL2 setting you have problem with ? Definitely it works out-of-the-box on MacOS and Linux, but if you are on WSL2 and if there are some specific settings, environment etc. it **might** have some errors - pretty much only you can find out what's wrong by looking at the logs. Usually k9s will show you them when you go to logs setting - sometimes - when you have crash loopback it might require you to try a few times, but I think using standard kubectl and k9s you should be able to see logs for failed pods as well. GitHub link: https://github.com/apache/airflow/discussions/52131#discussioncomment-13572708 ---- This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
