Dear Cloud Foundry Community,

We are nearing the completion of the v7 CF CLI and we’re excited to announce that we’ll be cutting our GA release soon!

 

The exact target date for the launch hasn’t been finalized but because transitioning from v6 to v7 will require coordination and planning we’re sending an initial heads up. We'll send follow ups to this communication once the launch date and associated details become concrete.

 

In case you haven’t been following the development of the v7 CLI closely, here’s three of many new capabilities that will become available when v7 GAs:

• Rolling Deploys using the "--strategy" flag for "cf push" and other commands

• Metadata apply labels and annotations to apps, spaces, organizations, and other resources

• Sidecar Processes for applications using application manifests

Current Plan:

1. We’ll continue working through and finalizing the finer-grained details regarding the transition from v6 to v7 (these details will be sent as a follow up to this announcement in advance of the v7 GA)

2. In the coming weeks, we’ll cut a feature complete v7 CLI release candidate (7.0.0-rc.1)

3. We’ll coordinate with Release Integration (RelInt) team to integrate the RC v7 CLI into their CF-Deployment CI pipelines and iterate on fixes as necessary ‘till they run green 

4. Once we’ve finalized and published the v6 to v7 transition plan & the RC v7 CLI has been passing successfully through RelInt’s CF-Deployment CI Pipelines, we’ll GA the v7 CLI

5. Once the v7 CLI is GA, the active development and release of new features and bug fixes will take place on the v7 CLI, and as per Phase 2 of the v6 CLI deprecation plan, the v6 CLI will no longer be under active development and only be updated to fix severe bugs and or CVEs

While our goal is for the v6 to v7 CLI transition to be fairly easy, it is a major version bump containing breaking changes and a certain amount of impact is unavoidable. 

The previously published “Upgrading to cf cli v7” describes many of the breaking changes that will be included at launch. Although the doc isn’t final, it’s the best resource currently for those needing to understand the change required in day to day manual and/or automated workflows.

 

At the time of this communication, although the list of breaking changes included in the document linked above is nearly complete, it should not be considered comprehensive.

Once we complete our final review/audit we’ll publish an exhaustive list of the changes from v6 to v7 and we’ll send an announcement to the community.   

Automated scripts may break when v7 of the CLI GAs. To minimize disruption and allow for teams to migrate when ready, we will support pinning to the 6.x major version. Although this isn’t possible today, the CLI team is actively working on this capability and will send a follow-up communication with instructions once that work is complete.

Lastly, with the GA release of v7, we plan to update the CF-CLI Minimum Supported Version policy. A separate communication describing the intended changes will be sent to this distribution list soon. 

For more information about the v7 CLI, please visit Cloud Foundry docs, message us on slack, or visit our github.

Thanks,

Cloud Foundry CLI Contributors

Hi,

 

I don’t think that using bits-service with the mentioned ops files will work. In fact support for bits-service is broken since cf-deployment v12.39 (incl. CAPI v1.92, more precisely commit https://github.com/cloudfoundry/cloud_controller_ng/commit/66fb2bd434656e8caa060ff55e6c87a296ab1455 that adds a new method which is not implemented in the Ruby BitsService::Client class). Is our observation correct or are we doing something wrong when setting up a current version of cf-d with bits-service?

 

Thanks,

Philipp

 

Hello everyone,

 

The Services API Team has been working on a model for the Cloud Controller V3 API for service bindings, service keys and service route bindings.
You can view the proposal here:

https://docs.google.com/document/d/115XMaCGvtkuXpmSA-UwnEowYdZ75mLB_OdXsuSiwRf4

We are seeking feedback from the community to help us finalize this proposal and move forward with implementation.

We are looking forward to your comments! You can contact us by replying to this email, or in our cloud foundry slack channel #svat 

Best regards
Felisia
On Behalf of the Services API Team

Hi Josh

Am 27.04.2020 um 18:13 schrieb Josh Collins:
> Dear Cloud Foundry Community,
>
>
> We are nearing the completion of the v7 CF CLI and we’re excited to
> announce that we’ll be cutting our GA release soon!

This is fantastic news. Our developers are waiting for some of the
experimental v3-commands to be replaced with stable CLI v7 commands.

> The exact target date for the launch hasn’t been finalized but because
> transitioning from v6 to v7 will require coordination and planning we’re
> sending an initial heads up. We'll send follow ups to this communication
> once the launch date and associated details become concrete.
>
>  
>
> In case you haven’t been following the development of the v7 CLI
> closely, here’s three of many new capabilities that will become
> available when v7 GAs:
>
>   *
>
>     Rolling Deploys
>     <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.cloudfoundry.org_devguide_deploy-2Dapps_rolling-2Ddeploy.html&d=DwIFaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=zV_urrEjeWCta68K3cScoA&m=YeWLNHeSMdg9ByYElGUn1Z6tYysmnfqN-WG7A9-Db50&s=d1K8PTiAZKqEa-ufU1Sba8TGGzX7Pae4jRJvPUFnfd8&e= >using
>     the "--strategy" flag for "cf push" and other commands
>
>   *
>
>     Metadata
>     <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.cloudfoundry.org_adminguide_metadata.html&d=DwIFaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=zV_urrEjeWCta68K3cScoA&m=YeWLNHeSMdg9ByYElGUn1Z6tYysmnfqN-WG7A9-Db50&s=bQHubdd5Qkr-cstS5XJkoF5b44i_kMuV3zRhS74OCB0&e= >apply labels
>     and annotations to apps, spaces, organizations, and other resources
>
>   *
>
>     Sidecar Processes
>     <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.cloudfoundry.org_devguide_sidecars.html&d=DwIFaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=zV_urrEjeWCta68K3cScoA&m=YeWLNHeSMdg9ByYElGUn1Z6tYysmnfqN-WG7A9-Db50&s=IpVJPQf06TQ78_X8hsiNmDipQAadSAK01KOI9lvxU9g&e= >for
>     applications using application manifests
>
> ...

How about manifest files? Do we have to expect any manifest syntax or
naming changes? Will some of the new CLI features also be available in
the manifest?

Thanks,

   Stefan

Hi All,

You may have seen Dr. Max's note earlier.  After leading Extensions PMC for almost four years, he would like to step down and make space for new folks to take on the role. 

Please send in your nominations for a new lead for Cloud Foundry Extensions PMC by the end of day next Friday, May 8, 2020. 

-- Swarna Podila (she/her)

Senior

 Director

, Community

 | Cloud Foundry Foundation

spodila

@cloudfoundry.org

@

skpodila

You can read more about pronouns here, or please ask if you'd like to find out more.

Hello CF community,

We just shipped cf-for-k8s 0.2.0 alpha release, so please check out the release notes here. Some notable highlights of this release,

- Users can now see streaming logs during cf push command. woot!

- Users can now see app metrics.

- Removed install.sh so users have the freedom to use ytt and kapp however they like (e.g. pass additional config of their choice)

There are many other updates worth looking into. Please take it for a spin and give us your feedback via issues or in slack channel #cf-for-k8s. 

Thank you to all the contributors!! 

Resources:

[1] Release notes for 0.2.0

[2] Slack channel # cf-for-k8s

--

Saikiran Yerram