-
Notifications
You must be signed in to change notification settings - Fork 30
Design Documents
Guillaume Berche edited this page Jun 21, 2023
·
249 revisions
- Cloud Controller API Semantic Versioning- Replaced by CAPI V3
- IBM Design Proposal for High Availability Policies in v2 - Not started
- Users and Roles Improvements - seems to have been removed?
- CC API V3 - Started details
- Event Notification - Not started
- Deployment and operations:
- Organization Blacklisting for Public Service Plans in CloudFoundry - Implemented (doc)
- Placement and isolation
- App Placement and High Availability Placement Pools - Old, the latest on this proposal is now in Elastic Clusters listed below
- Elastic Clusters
- Original CF elastic clusters proposal. Story
- Service Discovery within Elastic Clusters
- Workload isolation
-
Isolation segments - Completed
- Routing for Isolation Segments - Implemented
- V3 CC API adaptions for Isolation segments
- Loggregator Isolation - cf-dev@ thread
- CF Java client 2.0 redesign - Implemented
- Application Security Groups - Implemented (docs)
- App Containers - Warden Docker Comparsion - Implemented
- Performance Acceptance Testing Suite
- Notifications Component - Implemented & Deprecated
-
Diego - DEA Redesign - Implemented
- Docker images in Diego - Implemented
- Private Docker repositories - cf-dev@ thread
- See diego-design-notes for additional diego specs
- CF+Diego Components using etcd and Consul - Implemented
- Garden union file system - (Slack thread)
- Droplets & rootfs as OCI images - Starting
- Diego Cell API - (Slack thread)
- Garden Pods inception
- Diego 2.0 breaking changes (cf-dev thread)
- Use Containerd to run containers in Garden-RunC
- Readability Improvements to Diego Component Logs -
- CPU Sharing and Metrics in CF - cf-dev@ thread
- Enabling secure communication between Cloud Controller and Diego
- Env variable groups - Implemented
- CF Notifications Service - Implemented
- Bits and blobstore
- Container networking - Implemented
- Support of tasks
- Persistence:
- Application autoscaling service
- Application life cycle
- Application Releases and Rollback - HPE suggested. Not started. Replaced CAPI V3 ( cf-dev thread)
- Zero downtime application updates (cf-dev thread)
- Security
- CF Permissions incubation team
- CF Dev local Bosh/CF/Service deployment - cf-dev@ thread.
- Egress Policies with Service Brokers - Cf-dev@ thread
-
Metadata for Cloud Controller API Resources - Implemented user manual
- Metadata Workflows With CLI Options
- Metadata in application manifest story
- Server side app manifest - started cf-dev@ thread epic
- Advanced Deployment Strategies Proposal
- Cloud Foundry Service Broker v2 API - Complete (Documentation)
- Service Dashboard SSO - Complete (Documentation)
- Service Usage Events - Complete (Documentation)
- Update service instance (e.g. upgrade plan) - Complete (Documentation)
- Asynchronous Service Instance Provisioning - Complete (Documentation)
- Arbitrary Provision Parameters - Complete (Documentation)
- Provision credentials without bind (Service Keys) - Complete (Documentation)
- User-managed (Private) Service Brokers - In progress details
- Service Broker User delegation during provisionning ( cf-dev thread)- Not started
- Reducing state in service brokers
- Kubo: Kubernetes on bosh. Slides, cf-dev thread - Implemented
- Sharing services instances across orgs and spaces:
- Orphan service mitigation - Story
- Multi-Service Registration
- Async service bindings - Story
- Granular updates (sapi epic
- Independent service manager
- Services CAPI V3 VAT progress spreadsheet
- Improving
cf service
UX - Enhanced experience for Service Bindings in the CF CLI
Logging (see also loggregator project board)
- Application Logging with Loggregator - Implemented
- Go Runtime instrumentation - Implemented
- Metrics Architectural Direction (gone)
- Emitter Library for HTTP Proposal
- Emitter Library for Events
- cf-component resources and utilization
- initialization process for the emitter libraries
- Reliable logs - (cf-dev thread)
- Security logging - Done - Epic
- Tagged metrics
- Loggregator Health Check Nozzle
- Scalable syslog - Implemented - (cf-dev thread)
- Application metrics forwarding - (cf-dev thread )
- Firehose refinements:
- noisy neighbor measurements improvements (cf-dev thread)
- improved persistence architecture feature proposal (recent log par app caching, cf-dev thread))
- Proposal for PMC Incubation of Unified Logging
- Loggregator Isolation - cf-dev@ thread
- Syslog Drains for all Apps in a Space - cf-dev@
- Loggregator Service Drains
Buildpack life cycle - In progress Epic
- Cloud Foundry Buildpacks - Implemented
- ALM and CI Integration - Not started
- Mapping Buildpack dependencies - Implemented
- Buildpacks: binary audit trail epic - Implemented
- Staging & Runtime Hooks - Proposed (HP)
- Binary service broker
- Admin buildpack location - (HPE suggestion in cf-dev thread )
- Multiple buildpacks:
- Buildpack-related meta-data - Orange proposed - Addressed by CNB
- Private stacks - (Proposed by NTT, cf-dev@)
- CF Routing API
- Context Path Routing - Implemented (docs)
- Route Services - Implemented (docs)
- TCP Routing -
- Enhanced load-balancing
- Route integrity (Increasing Availability of Applications and the Platform Management plane during Failures with Route Registration)
- Mutual TLS between external clients and apps in CF - Complete
- Istio integration
- Technical Design for New Routing Control Plane leveraging Istio. - Implemented
- Cloud Foundry Integration with Istio Pilot and Envoy - Started
- Istio Router on the Container (Overlay) Network - Implemented
- Istio in CF-K8s
- Weighted Routing user experience in CF - cf-dev@thread
- Improving Security for HTTP Ingress to CFAR Application Containers - cf-dev@ thread
- See https://github.com/cloudfoundry/bosh-notes#bosh-notes for recent bosh design proposals
- Service Discovery in BOSH releases (2012)
- BOSH Bootloader for Operators
- BOSH-aware DNS server
- OSS BOSH Vision and Strategy 11-2018
- Lifecycle Management for k8s - cf-bosh@ thread
-
cf help
redesign (June-July 2016) - UX Routes in App Manifests (June-July 2016)
- Value Substitution in App Manifest Proposal
- removing --no-start from cf push in CLI v7
- New Deployment Workflows With CLI Options
- Terraform provider for Cloud Foundry - cf-dev@ thread
- MultiApps from SAP - cf-dev@ thread
- Simplifying Cloud Foundry Login Server
- Access Control Services suggested by Dario Amiri (GE) into vcap-dev thread
- UAA & SAML Integration for handling SAML claims. Complete. Epic
- CF leveraging LDAP groups/SAML claims to derive CF org/space role memberships a.k.a "CF Roles & LDAP/SAML"
- Revocable tokens
- Machine Authentication using UAA
- Invitations API
- UAA Js SDK aka OIDC Sessions / Single Sign Out - Done OIDC session management
- UAA integration with Kubernetes & Istio - Started
- Multifactor Authentication for UAA - Done Epic. google-authenticator support implemented
- cf-bosh@ thread
- TCP Routes for CFCR Services: Possible Workflows - cf-dev@ thread
- CFCR Control Plane BBR scenarios - Bloomberg - related story
-
CF for K8s: Index of CFF resources and discussions
-
Kubernetes-idiomatic⭐️ Cloud Foundry components guidelines
- Now published in cloudfoundry-incubator/kubernetes-guidelines repo
- Running app workloads across multiple K8s clusters via a single CF control plane
- CFAR Loggregator/Eirini co-evolution discussion notes
- Garden Security for Kubernetes/Eirini Inception
- Volume Services in CF4K8S
- cf-for-k8s Metrics Guide
- Exploring CRDs in the CF App Runtime
-
Kubernetes-idiomatic⭐️ Cloud Foundry components guidelines
- KubeCF to CFF KubeCF incubating CFF
- Nats message flow reference
- Metrics list transient reference
- Import-Path Service for Cloud Foundry Golang Repositories
- Word and Phrase List: Public Facing - Glossary/vocabulary used in documentation (Dos and don'ts)
- 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