potiuk commented on issue #22485:
URL: https://github.com/apache/airflow/issues/22485#issuecomment-1079963039
> This has nothing to do with pods started in `3.0.2`. The KPO is not able
to start new pods in `3.1.1`.
@sushi30 - it is very likely something environmental for you. People often
argue that "it worked before so it must be backwards compatibiliity problem"
where in fact there might be other - environmental factors where
misconfiguration or wrong deployment caused things to "work" (or rather mask
problem) before, only to be revealed when for example new library provides more
thoropugh check. Or maybe a library change causes some more resource usage and
you simply need to increase resources (memory/disk/the like). There can be many
things that could go wrong. I would not jump into conclusion this is backwards
compatibility. It might be, but does not have to - and it is not at all
obvious.
That would be rather surprising to have some general problem - we do not
see other people reporting problems like that one.
Do you have any logs telling more what's happening? Maybe you can take a
look at the logs of K8S creating PODs and maybe they will tell you what's
wrong. The informaton that PODs are "hanging" makes it impossible to diagnose
what's wrong - without more details we have even less information than you
have.
And looking at logs of what's happening when it fails is something that only
you can do, I am afraid. Also it would be great to get some more information -
which K8S version you have for example.
What I Can you also try the 2.2.5rc1 release of Airflow (We just put it up
for voting). The images we have in dockerhub contain both - latest Airflow and
latest cncf.kubernetes so if you could try it and see if the problem persists
there would be helpfi.
--
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]
