RFC for introducing "CF on KinD"

[c0d1ngm0nk3y]

Cloud Foundry local setup is currently cumbersome and has a steep learning curve. This makes it difficult for new users to get started and slows down component development. We propose a simple and fast way to run Cloud Foundry locally, providing a better first-time user experience. Additionally, this enables developers to rapidly prototype, develop, and test new ideas in an inexpensive setup.

preview

[beyhan]

One feedback from the TOC meeting is to have more precise description of the intended use case and where it doesn't make sense to use this for validation and testing for example.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: c0d1ngm0nk3y / name: Ralf Pannemans (bb421c2, e0c7bfb)
• ✅ login: mvach / name: Matthias Vach (7795910)
• ✅ login: sklevenz / name: Stephan Klevenz (16a60c7)

[beyhan]

The long term use case for this contribution has been addressed with 16a60c7

[PlamenDoychev]

It's not clear to me who we're targeting with this proposal.
Shouldn't we;

1. position it for those who want to do an initial CF try-out and experience "cf push" locally.
2. In addition to 1) target component developers as well but with some "limitations", because it will not be possible local development for all CF components.

[tlakner]

The RfC refers to CF Classic (and not CF Korifi). Suggestion is to also state this in the description more clearly.
I also agree to Plamen to state more clearly the main use case for CF on kinD - local development environment for CF component developers who get a lower entry barrier with this approach than before.

[loewenstein-sap]

Hi @tlakner,

thank you for your interest in this RFC. You say

The RfC refers to CF Classic (and not CF Korifi). Suggestion is to also state this in the description more clearly.

I would argue that "Cloud Foundry" without any additional attribute means the classical Cloud Foundry deployed by Bosh as we know it. Anyway, let me suggest we mention Bosh and cf-deployment explicitly to make this entirely clear.

I also agree to Plamen to state more clearly the main use case for CF on kinD - local development environment for CF component developers who get a lower entry barrier with this approach than before.

I would argue that we explicitly address first-time users and Cloud Foundry component developers in the Problem section. What else would you suggest in extent to the following?

• community/toc/rfc/rfc-draft-cf-on-kind.md

  Line 17 in 16a60c7

  First-time users encounter significant difficulty when they simply want to try out the `cf push` workflow. Currently, there is no local setup using existing community tools and technologies that can be ready within minutes.

• community/toc/rfc/rfc-draft-cf-on-kind.md

  Line 19 in 16a60c7

  Cloud Foundry component developers face long setup times and complex environments when testing their changes in an integrated environment. This slows down the development process and makes it harder to contribute to the Cloud Foundry ecosystem.

Best regards
Jan

[loewenstein-sap]

Suggested change

Cloud Foundry local setup is currently cumbersome and has a steep learning curve. This makes it difficult for new users to get started and slows down component development. We propose a simple and fast way to run Cloud Foundry locally, providing a better first-time user experience. Additionally, this enables developers to rapidly prototype, develop, and test new ideas in an inexpensive setup.

Cloud Foundry local setup with Bosh and cf-deployment is currently cumbersome and has a steep learning curve. This makes it difficult for new users to get started and slows down component development. We propose a simple and fast way to run Cloud Foundry locally, providing a better first-time user experience. Additionally, this enables developers to rapidly prototype, develop, and test new ideas in an inexpensive setup.

[loewenstein-sap]

Suggested change

	Setting up Cloud Foundry locally is currently cumbersome which creates a significant barrier to entry.
	Setting up Cloud Foundry locally using Bosh and cf-deployment is currently cumbersome which creates a significant barrier to entry.