Cloud Connector 17.9 planning

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Capacity

This milestone runs from 2025-01-13 ~ 2025-02-14

There is currently no team PTO planned for this time.

Planning

Indicate major efforts by linking to the appropriate epic. Under each epic indicate who is focusing on these efforts and list the individual issues assigned for this milestone.

Top Priorities for 17.9

FY26 Planning and beyond

Complete https://gitlab.com/gitlab-org/cloud-connector-team/team-tasks/-/issues/201+ and ensure alignment with stakeholders

Extract CloudConnector unit_primitive configura... (gitlab-org&14310 - closed)

We will complete Phase 2: Deliver and Publish the Ruby Gem for C... (gitlab-org&15636 - closed) making the SSOT for Unit Primitive configuration be our new repository. The work remaining is to update CDot to use the new Unit Primitive configuration, and stay aligned with the Data team on the changes as they migrate to the new SSOT.

We will begin Phase 3: Prepare unifying token issuance (gitlab-org&15637 - closed) This will likely require us to also work on refining plans for Custom Models since there are special cases in place for Self Hosted Models that will need to be addressed.

https://gitlab.com/groups/gitlab-org/-/epics/15142+

In 17.8 we have implemented the first improvements to OIDC discovery to improve reliability. Since this change is to a critical area, we decided to not roll out until January, so we will now complete this in 17.9. We have also identified follow up work that we will start in 17.10

https://gitlab.com/groups/gitlab-org/-/epics/16215+

We now have a planned approach for this work and will continue with this work, and refining this plan during 17.9

Additional Issues for consideration

Spike - move healthcheck out of subscription page (gitlab-org/gitlab#509361 - closed)

Puma memory work - we will continue to triage this issue and we may want to improve documentation and help on this. Might be worth setting up a sync on this topic with the respective teams.

Kickoff Video

• initial draft - PM/EM (Mon 2025-01-06)
• draft shared with team for review (Tue 2025-01-07)
• team sync discussion (Thu 2025-01-09)
• Planning is finalized and kickoff video is recorded (Thu 2025-01-16)