What is the end of life for CF V2 APIs?

[karthik-sub]

Question: We are using CF V2 APIs in our project. Given that V2 is deprecated we would like to know the end of life for V2 APIs? This info will help us to plan the upgrade accordingly. Thank you.

[Gerg]

I converted this to a discussion instead of an issue.

[Gerg]

In short, there are currently no plans to disable or delete the v2 API.

Based on our analysis, the effort to migrate all clients off of the v2 API is too large for the engineering resources that are currently available. We have successfully migrated a number of major open-source and proprietary clients to v3, but there are still numerous v2 clients that are in common use but are not actively maintained.

Since the v2 API is deprecated, it will not receive new features or bug fixes. As such, we recommend that client authors migrate to the v3 API as soon as possible.

[philippthun]

There is a configuration option to disable v2 endpoints. So even though they might still be supported by code, platform operators can decide to stop support in a specific foundation.

[Gerg]

Further discussion in the RFC: cloudfoundry/community#941

[stephanme]

RFC-0032 CF API v2 End of Life was accepted by the TOC.

tl;dr;
Predicted end-of-life for CF API v2 is mid/end 2026. Refer to the RFC for the complete roadmap which contains TOC checkpoints before CF API v2 finally gets removed from CAPI and cf-deployment.