-
Notifications
You must be signed in to change notification settings - Fork 31
v210
Shannon Coen edited this page Jun 9, 2015
·
4 revisions
The cf-release v210 was released on May 23rd, 2015
- Addressed USN-2617-1 CVE-2015-3202 FUSE vulnerabilities
- [Experimental] Work continues on support for Asynchronous Service Instance Operations details
- Support for configurable max polling duration
- [Experimental] Work continues on /v3 and Application Process Types details
- [Experimental] Work continues on Route API details
- [Experimental] Work continues on Context Path Routes details
- Work continues on support for Service Keys details
- Upgrade etcd server to 2.0.1 details
- Should be run as 1 node (for small deployments) or 3 nodes spread across zones (for HA)
- Also upgrades hm9k dependencies. LAMB client to be upgraded in a subsequent release. Older client is compatible.
- cloudfoundry/cf-release #670: Be able to specify timeouts for acceptance tests without defaults in the spec. details
- Fix bug where ssl enabled routers were not draining properly details
- cloudfoundry/cloud_controller_ng #378: current usage against the org quota details
- Apps no longer need to be unbound and rebound to receive new credentials when a user-provided service instance is updated. Apps only need to be restaged/restarted details
- Bumped to UAA 2.3.0 details
- BOSH Version: 152
- Stemcell Version: 2889
- CC Api Version: 2.27.0
- final release 0.1247.0 commit
- No need to ask permission - if you want to make an edit or add a new section, just do it!
- The official cf-docs maintainers cherry-pick content from this wiki for the official docs
- The contents of this wiki are in no way endorsed, maintained or supported by the core Cloud Foundry team
- Development Process
- Mailing Lists & Chats
- CI and the Commit Pipeline
- Contributing Code or Docs
- Contribution Standards
- Design Documents
- Proposing New Features
- Adding New Services
- Project Incubator
- Reporting Security Vulnerabilities
- CFF vulnerability mgt
- CAB meeting minutes
See CFF official project list.
Roadmaps are reflected in pivotal trackers. Tracker Instructions and steps to watch stories. Here is a flat list of all trackers:
- BOSH
- BBR
- CF Abacus
- CF App Autoscaler
- CF Buildpacks
- Concourse roadmap, and milestones
- CF Containerization/quarks
- CF Container Networking
- CF CAPI
- CF API K8s Evolution
- CredHub
- CF CLI
- CF CLI V3 acceleration
- CF Diego
- CF Docs
- CF Eclipse
- CF Eirini
- CF Flintstone
- CF Foundation
- CF Garden
- CF Greenhouse (windows)
- CF GrootFS (aka Garden RootFs)
- CF Identity (aka UAA)
- CF Infrastructure (incls BBL)
- CF Java Buildpack
- CF Java Client
- CF Lattice
- CF Logging and Metrics
- CF MEGA (Release Integration)
- CF Networking - CF K8S
- CF Networking - CFAR Mesh
- CF Mysql (core services)
- CF Notifications
- CF Permissions
- CF Persistence
- CF Postgres-release
- CF Runtime OG
- CF Routing
- CF Routing TCP
- CF services API (aka SAPI)
- Cloud Service Brokers (by SAPI/service enablement team)
- Kubo
- License Finder
- BBR
- Buildpacks
- BOSH
- BOSH CPIs
- Cf Java Client
- Core services (mysql) - repo
- Garden
- Grootfs
- Infra/tools
- Java Buildpack
- Kubo - repo
- Loggregator
- Persistence
- Release integration - repo
- Routing
- Runtime - repo
- Service API (aka SAPI)
Maybe other CIs hosted on cf-app.com are mentioned in slack ?
- See Client Tools on docs
- 3rd Party Compatible Apps