Adding a dependent library to a Job task permanently adds it to the entire cluster?

- - Certifications
- - Learning Paths
- - Databricks Product Tours
- - Get Started Guides
- - Product Platform Updates
- - What's New in Databricks

- - Get Started Resources
- - Events
- - Support FAQs
- - Technical Blog
- - Knowledge Sharing Hub
- - Announcements
- - DatabricksTV

- - Private Groups
- - Skills@Scale

- - Databricks Community Champions
- - Khoros Community Forums Support (Not for Databricks Product Questions)
- - Databricks Community Code of Conduct

Data Engineering

Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.

Why does adding a dependent library to a Job task also permanently add it to the entire cluster?

I am using python wheels, and even when I remove the dependent library from a Job task, the wheel is still part of the cluster configuration.

If I then update the version of wheel used by the task, I then shows multiple versions of the wheel in the cluster libraries. I have no way to know which one is being used.