|
Re: CF on K8s Update
Jan von L?wenstein
Hi Angela et al,
It is good to have clarity on the state of cf-for-k8s for which a decline in activity has been observable
already for some time.
Additionally, freeing up resources for the broader topic of exploring further options of bringing the Cloud Foundry workflows to Kubernetes is
a good decision.
What makes Cloud Foundry awesome?
In my humble opinion, it is the not having to care. Not having to care how code is translated into an executable container. Not having to care how such container is executed.
Now I would argue that we can reach eighty percent of the awesomeness of not caring for container creation using Paketo buildpacks with
pack on a developer machine and some integration into CI/CD - be it Jenkins, Concourse, Tekton, or something else.
Using
pack works nicely for the development flow and the production flow anyhow runs in a CI/CD system.
Similarly, I would argue that taking a container and creating a Kubernetes Workload resource (Deployment or StatefulSet) with secure container
defaults (runAsNonRoot and dropCapabilities: ALL to name two), the best available Kubernetes means to achieve high availability, and others will bring the largest part of value. Basically, what Eirini does.
In contrast, building container images on the server side and threading a call to
cf push through a cascade of custom resources and corresponding controllers seems to contribute a lot of complexity while provided only marginally to the value. Both, for the application developers/system operators and for the CF community developing
and maintaining these controllers.
Should we maybe focus our efforts on the creation of Kubernetes resources with good defaults for Cloud Foundry apps - doesn't even have to be
a controller, but handled in a CLI - and keep the layer(s) between the CF manifest and application code on the one hand side and the Kubernetes resources and application images on the other hand side as minimal and narrow as possible?
If the answer to the question of what's left of Cloud Foundry then is "Not much in terms of code", I would consider that a good thing.
Best regards
Jan
From: cf-dev@... <cf-dev@...> on behalf of Angela Chin <angelac@...>
Sent: 23 August 2021 19:24 To: cf-dev@... <cf-dev@...> Subject: [cf-dev] CF on K8s Update Hi cf-dev, Earlier this year, leadership from IBM, SAP, and VMware shared a new Vision for CF on K8s document and discussed it with the community. Since then, our group of engineers at VMware and SAP have been exploring what it would take to support this vision. We have been engaging in the CF on K8s SIG meetings to discuss future technical direction and spiking out a proof-of-concept to support the core cf push workflow using Kubernetes-native concepts, which you can view here. We are excited to share that we have finished the proof-of-concept and have recorded a demo video to illustrate. Additionally, we have written a high-level summary of the current architecture and have opened a PR for an initial set of CF CRDs. All of this work is being actively tracked in the CF on K8s Github project. We are looking to engage a larger swath of the community in our efforts, and would appreciate any and all contributions to this effort :) If you're interested in contributing to this effort, please join us in the new #cf-k8s-dev channel in the CF Slack! As a result of devoting development resources to accelerate this new vision and technical architecture for CF on K8s, we have decided to pause our contributions to the cf-for-k8s project. It is now in a position where it is stable and demonstrates the promise of the CF developer experience on top of Kubernetes. We anticipate future development to consist of only a small amount of regular maintenance to keep up to date with the latest versions of some of the dependencies it incorporates, such as Istio and kpack. We recently updated to the latest version of Istio but would appreciate additional community assistance in maintaining cf-for-k8s as we focus on bootstrapping the new CF on K8s architecture and reference deployments. We expect this activity to happen in the App Runtime Deployments working group that is forming under the new CFF technical governance structure. - Angela Chin, on behalf of the cf-for-k8s and Eirini maintainers |
|
|
|
cf CLI v7.3.0 is now available
Alexander Berez
Good Day to
You All,
Highlights:
Bug Fixes:
Contributors:
Reid Mitchell, Jenna Goldstrich, Alexander Berezovsky, Dominic Roberts, Juan Diego Gonzalez, Hema Ranganathan, Teal Stannard, Seth Boyles, Zach Robinson, Felisia Martini, George Blue, Sarah Weinstein, Colin Simmons and Ryker Reed
And as always, we really would
love to hear from you so please feel free to respond to this email or find us in the Cloud Foundry Slack #cli channel
any time.
Thank you very much
|
|
|
|
CF on K8s Update
Angela Chin
Hi cf-dev, Earlier this year, leadership from IBM, SAP, and VMware shared a new Vision for CF on K8s document and discussed it with the community. Since then, our group of engineers at VMware and SAP have been exploring what it would take to support this vision. We have been engaging in the CF on K8s SIG meetings to discuss future technical direction and spiking out a proof-of-concept to support the core cf push workflow using Kubernetes-native concepts, which you can view here. We are excited to share that we have finished the proof-of-concept and have recorded a demo video to illustrate. Additionally, we have written a high-level summary of the current architecture and have opened a PR for an initial set of CF CRDs. All of this work is being actively tracked in the CF on K8s Github project. We are looking to engage a larger swath of the community in our efforts, and would appreciate any and all contributions to this effort :) If you're interested in contributing to this effort, please join us in the new #cf-k8s-dev channel in the CF Slack! As a result of devoting development resources to accelerate this new vision and technical architecture for CF on K8s, we have decided to pause our contributions to the cf-for-k8s project. It is now in a position where it is stable and demonstrates the promise of the CF developer experience on top of Kubernetes. We anticipate future development to consist of only a small amount of regular maintenance to keep up to date with the latest versions of some of the dependencies it incorporates, such as Istio and kpack. We recently updated to the latest version of Istio but would appreciate additional community assistance in maintaining cf-for-k8s as we focus on bootstrapping the new CF on K8s architecture and reference deployments. We expect this activity to happen in the App Runtime Deployments working group that is forming under the new CFF technical governance structure. - Angela Chin, on behalf of the cf-for-k8s and Eirini maintainers |
|
|
|
Bosh proposal for enhancement of rotating bosh-agent certificates/credentials
Joseph Palermo
Hey all, we’ve got a proposal out for how to enhance the process of rotation certificates/credentials used by the bosh agent (making NATS cert rotation easier being the primary driver): https://github.com/cloudfoundry/bosh/discussions/2309Looking for feedback. Ideally we’d like to keep the conversation around it in the github discussion so it’s more permanent and discoverable. |
|
|
|
COMING SOON: V8 Release of CF CLI
dominicr@...
Hello all,
We are happy to announce that the CF CLI team is preparing to release v8 in the next month or so. Here are some new features that you can look forward to:
|
|
|
|
CFF Working Groups: feedback and participants requested!
Hi, everyone,
As we mentioned at CF Summit last week, the newly formed Technical Oversight Committee (TOC) is currently carrying out more and more of the details of the transition from the previous project-team and project management committee (PMC) structure to the working
groups and community roles.
To that end, we have proposed an initial set of working groups on
PR #140 on the community repo, together with how they will subsume the existing project teams and components. As a community, we now need to confirm the scope of each of these working groups, to staff them with leads and approvers, and to get them up and
running with transparent development and roadmap processes. Consequently, we need a few things from the community now:
We're currently working out these details for the App Runtime Deployments working group as a pilot case, so if you care about
cf-deployment, KubeCF, cf-for-k8s, or the overall community mandate to provide reference deployments of the App Runtime, now is the right time to get involved! The TOC would also like
to complete this process for the complete set of working groups over the next few weeks, so if you're more focused on another area of the CF community, we need your involvement as well.
We invite everyone to join to discuss these working-group proposals at the public TOC meetings every Tuesday at 10:30 am ET, with details on the
CF community calendar, and to provide feedback asynchronously on a particular proposed working group is the draft PR for its charter. Here is the full list of those charter PRs:
Please don't worry if you don't see a particular project listed here: it should be present in the PR content itself, and if it's not, the TOC wants to know about it!
Thanks,
Eric Malm, TOC member |
|
|
|
Cloud Foundry Community Awards Nominations is now extended!
Shedrack Akintayo <sakintayo@...>
Hello Friends,
The Community Awards nomination form deadline is now extended until Friday, July 2nd, 11:59 PM PT, 2021. This is to give our community members more time to nominate their peers as we strongly believe in the opinion of every community member. If you believe a particular member of the community deserves any of the awards, go ahead and nominate them. I also wrote a post to help answer any questions you may have about any of the award categories, but please feel free to reach out if there is any additional question. Get nominating today! Thanks, Shedrack. Shedrack Akintayo | Developer Advocate Cloud Foundry Foundation |
|
|
|
CFF TOC Meetings
Chip Childers <cchilders@...>
All, The newly elected CFF TOC will initially be meeting weekly, on Tuesdays at 14:30 UTC (7:30 AM US Pacific Time, 4:30 PM Central European Time). These meetings are open to the entire community to attend, although I ask that you respect that the TOC will be setting the agenda and running the meeting. The meetings will be recorded and posted to the foundation's youtube channel. Chip Childers Executive Director Cloud Foundry Foundation |
|
|
|
Re: Update regarding Bionic Stemcells: Version 1.10 released from Foundation owned infrastructure
Congrats Felix and SAP team, and all other CFF contributors for this great achievement!
toggle quoted message
Show quoted text
Benjamin
|
|
|
|
Update regarding Bionic Stemcells: Version 1.10 released from Foundation owned infrastructure
Riegger, Felix
Dear Cloud Foundry community,
The migration of the Stemcell release infrastructure and pipelines from VMWare to CloudFoundry Foundation owned accounts is mostly done. With Bionic Stemcell 1.10 the first Stemcell has been created and released with the new setup.
This is again a huge step forward to bring the Stemcell into the hands of the communitiy. Again a big thank you to everyone involved in this journey.
What has changed?
The new Stemcells are now published in Google Cloud Storage instead of AWS S3. This change uncovered a bug in the BOSH CLI, which has been fixed in the latest version. Please update to https://github.com/cloudfoundry/bosh-cli/releases/tag/v6.4.4 to consume the latest Stemcells.
In the previous setup BOSH Acceptance Tests (BATS), IPv4 and IPv6 tests have been executed against a vSphere environment owned by VMWare. In the new setup these tests are executed in a GCP environment. Unfortunately, it was not possible to replicate the IPv6 tests to this environment. While we don't expect big changes in this area this implies that IPv6 might stop working at some point with newer Stemcells without us noticing. If this is important to you and you would like to contribute please reach out to discuss options.
Where can I access the new infrastructure?
The concourse is hosted on https://bosh.ci.cloudfoundry.org/ and runs on a GCP account of the CloudFoundry Foundation.
Where is the code?
The repositories for the pipeline definitions and the stemcell code itself have not changed. They can be found in https://github.com/cloudfoundry/bosh-stemcells-ci and https://github.com/cloudfoundry/bosh-linux-stemcell-builder.
Any assets regarding the Concourse setup live in https://github.com/cloudfoundry/bosh-community-stemcell-ci-infra.
Who can access the pipelines and contribute?
Any member of https://github.com/orgs/cloudfoundry/teams/bosh-stemcell can access and work with the pipeline as well as the relevant repositories. If you would like to become a contributor, please reach out.
Where can I follow?
Work can be tracked in https://github.com/orgs/cloudfoundry/projects/4.
Anything else?
As was announced by the CFF Security Working Group in https://www.cloudfoundry.org/blog/security-advisory-update/ CFF security advisories are now in place for Bionic Stemcells and the release of version 1.10 triggered the first advisories.
Kind regards, Felix |
|
|
|
The Community Awards Nomination is Now Open
Shedrack Akintayo <sakintayo@...>
Hello Friends,
The Community Awards nomination form is now available! This means that you can nominate any of your peers in the community for any of the award categories available. If you believe a particular member of the community deserves any of the awards, go ahead and nominate them. The deadline for nominations is Friday, June 25th, 11:59 PM PT. I also wrote a post to help answer any questions you may have about any of the award categories, but please feel free to reach out if there is any additional question. Get nominating today! Thanks, Shedrack. Shedrack Akintayo | Developer Advocate Cloud Foundry Foundation |
|
|
|
Re: 2021 CFF Technical Oversight Committee Election Results
Lee Porte
Wow! Thank you to the community. I'm looking forwards to getting started Cheers L On Thu, 17 Jun 2021 at 13:53, Chip Childers <cchilders@...> wrote:
--
|
|
|
|
2021 CFF Technical Oversight Committee Election Results
Chip Childers <cchilders@...>
Many thanks to everyone who took the time to register and vote in the first Cloud Foundry Foundation annual election for our newly forming Technical Oversight Committee (TOC). I also extend my deep thanks to all of the nominees who agreed to run in the election. Overall, our community’s participation in this election process was outstanding (especially given that this was our first time doing this!) And with that preamble, I’m pleased to announce our first CFF Technical Oversight Committee will be: * Eric Malm (VMware) * David Stevenson (VMware) * Jan von Loewenstein (SAP) * Stephan Merker (SAP) * Lee Porte (GOV.UK) Congratulations to Eric, David, Jan, Stephan and Lee! I’m looking forward to working with you to get the TOC up and running. For transparency, more details have been published here: https://github.com/cloudfoundry/community/blob/main/toc/elections/2021/results.md Chip Childers Executive Director Cloud Foundry Foundation |
|
|
|
LAST CALL for CFF TOC election - Polling closes tomorrow
Chip Childers <cchilders@...>
Hi all! A reminder for the community that this is the last call for the TOC election. We've had a solid response rate for qualified voters voting, but there are 37 incomplete ballots (people that authorized their email address, but have not yet actually voted). I'll be closing the poll tomorrow, Tuesday June 15, at the end of the work day Pacific US time (around 5 PM US Pacific). If you are a qualified voter and have any questions or concerns, please let me know ASAP! Happy voting! Chip Childers Executive Director Cloud Foundry Foundation |
|
|
|
IMPORTANT NOTICE: [php-buildpack] End of Support for NGINX versions 1.18.x and 1.19.x after 2021-07-04
Amelia Castilla <acastilla@...>
The first release of the PHP buildpack after 2021-07-04 will no longer include NGINX versions 1.18.x and 1.19.x. These NGINX versions will no longer be supported upstream[1]. Please migrate your PHP apps to supported versions of NGINX before that time. Note: As 1.19.x is the current default version of NGINX in the buildpack, the default NGINX version will be updated to 1.20.1 as a part of this removal. If you’d like to use a different NGINX version, please configure your application to select that version[2]. As always, the Buildpacks team is happy to answer questions you may have about this deprecation in the #buildpacks Slack channel[3]. [1] - https://nginx.org/en/download.html [2] - https://docs.cloudfoundry.org/buildpacks/php/index.html [3] - https://cloudfoundry.slack.com/archives/C02HWMDUQ Thanks, The Buildpacks Team |
|
|
|
IMPORTANT NOTICE: [r-buildpack] End of Support for R versions 4.0.x after 2021-07-03
Elliott Shanks <shankse@...>
The first release of the R buildpack after July 3, 2021 will no longer include R versions 4.0.x. These R versions will no longer be supported upstream.[1] Please migrate your R apps to supported versions of R before that time. As always, the buildpacks team is happy to answer questions you may have about this deprecation in the #buildpacks Slack channel. [1] - https://developer.r-project.org/ For more information on r dependencies and their deprecation dates, please refer to https://buildpacks.cloudfoundry.org/#/buildpacks Thanks, Buildpacks Team |
|
|
|
IMPORTANT NOTICE: [staticfile-buildpack] Change of default nginx version after 2021-07-09
Amelia Castilla
The default version for NGINX will be updated to 1.21.x in the first release of the Staticfile buildpack after 2021-07-09.
We are giving a 30 day notice to inform users that the default version of NGINX in the Staticfile buildpack will be updated to the latest 1.21.x version in the first release of the Staticfile buildpack after 2021-07-09.
As always, the buildpacks team is happy to answer questions you may have about this deprecation in the #buildpacks Slack channel[1].
[1] - https://cloudfoundry.slack.com/archives/C02HWMDUQ
Thanks,
The Buildpacks Team |
|
|
|
IMPORTANT NOTICE: [nginx-buildpack] Change of default nginx version after 2021-07-09
Amelia Castilla
The default version for NGINX will be updated to 1.21.x in the first release of the NGINX buildpack after 2021-07-09.
We are giving a 30 day notice to inform users that the default version of NGINX in the NGINX buildpack will be updated to the latest 1.21.x version in the first release of the NGINX buildpack after 2021-07-09.
If you’d like to use a different NGINX version, please configure your application to select that version.[1]
As always, the buildpacks team is happy to answer questions you may have about this deprecation in the #buildpacks Slack channel[2].
[1] - https://docs.cloudfoundry.org/buildpacks/nginx/index.html
[2] - https://cloudfoundry.slack.com/archives/C02HWMDUQ
Thanks,
The Buildpacks Team |
|
|
|
IMPORTANT NOTICE: [php-buildpack] Change of default nginx version after 2021-07-09
Amelia Castilla
The default version for NGINX will be updated to 1.21.x in the first release of the PHP buildpack after 2021-07-09.
We are giving a 30 day notice to inform users that the default version of NGINX in the PHP buildpack will be updated to the latest 1.21.x version in the first release of the PHP buildpack after 2021-07-09.
If you’d like to use a different NGINX version, please configure your application to select that version.[1]
As always, the buildpacks team is happy to answer questions you may have about this deprecation in the #buildpacks Slack channel[2].
[1] - https://docs.cloudfoundry.org/buildpacks/php/gsg-php-config.html
[2] - https://cloudfoundry.slack.com/archives/C02HWMDUQ
Thanks,
The Buildpacks Team |
|
|
|
Re: CFF TOC Election Starting
Chip Childers <cchilders@...>
Not until the 15th... ;) Chip Childers Executive Director Cloud Foundry Foundation On Tue, Jun 8, 2021 at 8:40 AM 'Thun, Philipp' via open-service-broker-api <open-service-broker-api@...> wrote:
|
|
|