Since upgrading dagster from version 1.5.14 to 1.6.2 jobs are taking much longer to be finished using a celery-k8s setup. are there known issues regarding this setup up?

We are not aware of any specific issues related to the celery-k8s setup that would cause jobs to take significantly longer to finish as a result of upgrading from Dagster version 1.5.14 to 1.6.2 based on the documentation. However, performance issues can be complex and may arise from a variety of factors. To troubleshoot this issue, you might want to consider the following steps: 1. Review Release Notes: Check the [changelog](https://docs.dagster.io/changelog) for any breaking changes or bug fixes between the versions that might affect performance. 2. Check for Known Issues: Look at the [Github Issues](https://github.com/dagster-io/dagster/issues) for any reported problems that match your experience. 3. Monitor Resources: Use monitoring tools to check if there are any resource constraints in your Kubernetes cluster that might be causing the slowdown. 4. Review Code Changes: If you made any changes to your Dagster jobs or related code during the upgrade, review those changes to ensure they are not contributing to the performance issue. 5. Debugging Tools: Utilize tools like

py-spy

to profile your code and identify potential bottlenecks, as suggested in the [discussions](https://github.com/dagster-io/dagster/discussions). 6. Dagster Community: Engage with the Dagster community through [Github Discussions](https://github.com/dagster-io/dagster/discussions) to see if others have encountered similar issues and to seek advice. If you continue to experience issues, consider providing more detailed information about your setup and the behavior you're observing, which could help in diagnosing the problem.