cancel
Showing results for 
Search instead for 
Did you mean: 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 

Unity Catalog - Cluster Access Mode - Change Management

NOOR_BASHASHAIK
Contributor

Hi all,

I am curious to know how you handled change management when rolling out changes to cluster access modes (single user, shared) applicable to UC, especially when there is a centralized platform team offering Infrastructure Deployment services via DevOps for around 20+ projects building their use cases in Databricks Lakehouse.

I am trying to decouple the changes to cluster access modes, and roll-out those even before the UC upgrade starts, so the projects can deploy their Databricks jobs/workflows in "Single User" access mode already in Non-UC enabled workspaces (like they do currently on high concurrency, table acl enabled clusters with external hive metastore). Even though I notice "Single User" access mode in Non-UC workspaces, it seems I cannot use it against the cluster policy of existing table acl enabled clusters with external hive metastore.

If this is not possible, then the option I think of is having a flag in the CI/CD code that signifies which environment (DEV/QAS/PRD) is UC enabled, and accordingly deploy jobs/workflows accordingly with appropriate cluster access modes.

0 REPLIES 0
Join 100K+ Data Experts: Register Now & Grow with Us!

Excited to expand your horizons with us? Click here to Register and begin your journey to success!

Already a member? Login and join your local regional user group! If there isn’t one near you, fill out this form and we’ll create one for you to join!