potiuk commented on issue #16176: URL: https://github.com/apache/airflow/issues/16176#issuecomment-1362733780
You myst check your logs on K8S - this is absolutely normal for you as someone who manages k8s installation to fix any problems and be able to diagnose this. You have to learn it I am afraid @beascar. Various tools (kubectl, helm, k9s) are useful for that and your job is basically to master them. You chose k8s as your deployment, so you need to understand how to diagnose various problems there as a consequence. I cannot solve and diagnose your k8s installation for you, but If you are not familiar with using kubectl (you should eventually), one useful tool to use is `helm install --dry-run` - it will show you the resources that Helm chart creates after applying all the templates - just find the right Pod/container and you will find what image it pulls. And you can also check this way what are the resources created by helm. K9s is also useful to look at your k8s installation in "exploratory" way - and it allows to learn how k8s works much faster. Good luck with the diagnoses. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
