potiuk commented on issue #45812: URL: https://github.com/apache/airflow/issues/45812#issuecomment-3904624249
> > If I'm not mistaken, the purpose of dry run is to simulate running in a real environment, so you must give a credential (or kube config), if not, then where do you want it to run? > > You do not need credentials nor connection to any real or test k8s environment. You can dry run in a sense that pod spec validates and has no syntax or type errors. There is no way to actually simulate full run in dry run, as that would require full clone of production setup. > > We use dry run to just make sure that all functions execute, there are no undefined variables, or undefined functions / modules used for example. And for tasks,that all passed arguments are correct (name, value and type). And check that there are no cycles, or other dag issues. Again. Opening PR is a good idea here. This is hte best way to get a discussion going if your proposed solution will work - especially if you try it in your environment. There is little sense in waiting for a mythical "kubernetes maintainer" to discuss it with. this is such a small change, that showing a working PR that whoever can comment on, showing th extent of change it introduces and something tested in your environment, is the fastest way to get this one implemented. -- 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]
