CAPI K8s Release v0.4.0

Highlights

• Enforce CF CLI v7 as the minimum supported version in cf-for-k8s
• Support upload, deletion, and cleanup of expired packages from the configured package registry (except DockerHub deletion)
• All component images are now built with paketo buildpacks
• k8s secrets used for all credentials

Known Issues

• Package copy is not supported yet when package registry is configured details
• Buildpack apps with custom start commands don't have PATH set correctly details
• Process commands not displayed correctly by /v3/processes/PROCESS_GUID details
• Droplet upload and download not yet supported details
• API can report stack incorrectly details

CC API Version: 2.155.0 and 3.90.0-rc

Service Broker API Version: 2.15

CAPI K8s Release

• As a platform engineer, I'd like to enable debug logging for all CC components details
• given a package registry is configured, packages uploaded to CC are uploaded to the package registry details
• cloudfoundry/capi-k8s-release #44: CF API returns 500 if UAA server certs secret not provided details
• cloudfoundry/capi-k8s-release #58: Allow skip_cert_verify to be configurable so operators can decide if they want to skip ssl validation details
• Prevent access to internal endpoints when running on Kubernetes details
• Operator can validate that inconsistencies in Route desired state are eventually represented in the K8s API details
• Job queue metrics are often missing details
• cloudfoundry/capi-k8s-release #65: Set memory and cpu requests and limit values for all containers details
• all cf-api-server containers should run as UID 1000 details
• cloudfoundry/capi-k8s-release #68: remove eirini cert defaults details
• Ensure that minimum supported CLI version is v7 for cf-for-k8s details
• audit capi-k8s-release/templates/ccng-config.lib.yml for security issues [timebox 1 day] details
• API client receives an error when trying to start/stage an app using the v2 API on cf-for-k8s details
• Add script to tarball for dealing with metadata to json and to diff details
• Create a go web server that, given a path to a tarball, creates an oci image details
• Create a mechanism to delete OCI images from a registry details
• Explore the QoS options for components using resource requests/limits to determine the best scheduling option for system components details
• Move our stuff to CAPI details
• Refactor cf package in cf-api-controllers to use ginkgo details
• Remove diego config on cf-for-k8s details
• Remove cc_service_key_client_secret from k8s configmap details
• Remove metric-proxy cert generation from hack script and update CAPI client details
• Support kpack >= 0.1.x in capi-k8s-release details
• UAA Client password in cf-api-controllers should be a k8s secret details
• cloudfoundry/capi-k8s-release #61: Create NOTICE details
• cloudfoundry/capi-k8s-release #63: Remove TLS for metric-proxy details
• extract a unit tested layer from cf-api-controllers/{build,images}_controllers.go details
• refactor config loading in cf-api-controllers details
• rename cloudfoundry/capi-kpack-watcher image on Docker Hub? details
• rename package-image-uploader to registry-buddy details
• reorganize capi-k8s-release ServiceAccounts & Bindings details
• write draft ADR for k8s->CCDB route sync details

Cloud Controller

• /apply_manifest endpoint throws 500 error when manifest with metadata is provided details
• API client can order apps by state details
• API client can filter a variety of resources by created_ats and updated_ats details
• API client can filter a variety of resources by guids details
• API client can filter audit events that did NOT target a resource with a given target guid details
• API client can filter feature flags by updated_ats details
• API client can see validations when generating a manifest diff details
• Admin users should be able to list routes in a performant manner for large environments details
• Explore Order-by work for all resources details
• Review PR: cloudfoundry/cloud_controller_ng #1787: Add audit events for Apps#show_env and Revisions#show_environment_variables details
• Scaling a process with extreme memory results in an UnknownError details
• Staging apps using v3 should respect memory specified in the application manifest details
• cf apply-manifest throws 500 error when manifest with services is provided details
• v3 Add a link to details in service credential binding response details
• v3 Add link to parameters in service credential binding response details
• v3 Binding while other operations are in progress details
• v3 Create service cred binding between app and MSI sync details
• v3 Create service cred binding between app and UPSI (2/2) details
• v3 Filter service credentials bindings list by service offering details
• v3 Filter service credentials bindings list by service plan details
• v3 Get details of a service credential binding created in originating space details
• v3 Get details of a service credential binding created in shared to space details
• v3 Get details of a service credential binding that includes credhub ref details
• v3 Get parameters of a service credential binding details
• v3 Handling last operation response on create route binding details
• v3 Include service instance resources when retrieving service credential bindings details
• v3 Orphan mitigation on failed route bindings details
• v3 Route binding while other operations are in progress details
• v3 Unbind service credential binding for UPSI details
• v3 Validate request to create service cred binding between app and MSI details
• v3 Validate request to create service cred binding between app and UPSI (1/2)...

CAPI K8s Release v0.3.0

Highlights

• Ability to specify buildpack when pushing
• Automatic stack updates
• List CNB buildpacks via API
• App health check events

CC API Version: 2.153.0 and 3.88.0-rc

Service Broker API Version: 2.15

CAPI K8s Release

• API user can see a list of available CNBs details
• Auto-Update App's StatefulSet with new OCI image resulting from stack update details
• Consumer of app metrics can add tags via labels details
• Developer can specify what buildpack to build with details
• Reconcile cf-api-controllers loggers details
• Refactor cf package in cf-api-controllers details
• Refactor kpack-watcher to use kubebuilder details
• Remove metric-proxy cert generation from hack script and update CAPI client details
• Run horizontal scaling experiments for cf api server in cf for k8s [timebox 4 days] details
• Support cf restart after stack updates details
• UAA Client password in cf-api-controllers should be a k8s secret details
• UAA Client password in cf-api-kpack-watcher should read from files instead of env vars details
• build a ship-it button and cut a capi-k8s-release from ci-passed details
• build controller occasionally doesn't send build updates details
• capi-k8s-release shouldn't need certificates to talk to OPI details
• cloud controller secrets should be k8s secrets details
• cloudfoundry/capi-k8s-release #42: Make blobstore provider configurable details
• cloudfoundry/capi-k8s-release #43: Enable TLS for database details
• cloudfoundry/capi-k8s-release #43: Enable TLS for database details
• cloudfoundry/capi-k8s-release #47: Revert "Make blobstore provider configurable" details
• cloudfoundry/capi-k8s-release #50: Change kpack registry repository key details
• cloudfoundry/capi-k8s-release #51: Remove certs for metric proxy details
• cloudfoundry/capi-k8s-release #54: Add missing namespace to database-ca-cert details
• cloudfoundry/capi-k8s-release #57: remove opi certificates from capi-k8s-release details
• cloudfoundry/capi-k8s-release #59: more renaming of cf-api-kpack-watcher -> cf-api-controllers details
• cloudfoundry/capi-k8s-release #60: cf-api-controllers sometimes fail to notify CAPI of incomplete builds details
• cloudfoundry/capi-k8s-release #64: External blobstore preparations details
• create ADR to decide where to place the source for kpack-watcher and future k8s-related code we might own [details](https://www.pivotaltracker.com/story/show/172965854

Cloud Controller

Cloud Controller Database Migrations

Pull Requests and Issues

CAPI K8s Release v0.2.0

Highlights

CC API Version: 2.151.0 and 3.86.0-rc

Service Broker API Version: 2.15

CAPI K8s Release

None

Cloud Controller

• Emit app events in a way that is consumable by cf-for-k8s logging details
• Review and update the upgrade guide details
• Review and update the v3 API docs details

Cloud Controller Database Migrations

None

Pull Requests and Issues

None

CAPI K8s Release v0.1.0

Highlights

CC API Version: 2.151.0 and 3.86.0-rc

Service Broker API Version: 2.15

CAPI K8s Release

• Add available buildpacks to CF-for-k8s Store & Custom Builder details
• Detect process_types from kpack-built image metadata details
• Emit app events in a way that is consumable by cf-for-k8s logging details
• Ensure statsd exporter image uses an approved base image. details
• build a ship-it button and cut a capi-k8s-release from ci-passed details
• make ccng's service account NOT a superuser (i.e. not cluster-admin) and only need [mostly] whatever permissions it needs details
• rotate the certs for our concourse director and everything it's deployed details

Cloud Controller

• API client author can see information in the upgrade guide about how to use audit events on v3 details
• API client author can see information in the upgrade guide about how to use usage events on v3 details
• API client author can see information in the upgrade guide about what happened to v2 summary endpoints and how to upgrade away from them on v3 details
• API client can clear the buildpack cache details
• API client can discover app usage events on the v3 API details
• API client can discover service usage events on the v3 API details
• API client can discover usage events on the v3 API details
• API client can download droplets on the v3 API details
• API client can filter app usage events details
• API client can filter service usage events details
• API client can filter usage events details
• API client can list app usage events details
• API client can list service usage events details
• API client can list usage events details
• API client can purge and reseed app usage events (create an epoch) details
• API client can purge and reseed service usage events (create an epoch) details
• API client can see data for a service usage event details
• API client can see data for an app usage event details
• API client can view a service usage event details
• API client can view a service usage event details
• API client can view an app usage event details
• API client can view an app usage event details
• API client can can filter app usage events using after_guid details
• API client can can filter service usage events using after_guid details
• API client can create a route with a random port on the v3 API details
• API client can see links on usage events details
• API client can see permissions for an app details
• API client can see a global summary of memory and instance usage across the whole platform details
• API client receives helpful messages when CC has difficulty talking with Routing API when interacting with routes. details
• API client sees an error when creating a route with a host or path for a TCP domain details
• API client should NOT see download link for droplets with docker lifecycles details
• API client should see a helpful error when attempting to download a droplet with a docker lifecycle details
• API make MySQL unit tests less flaky details
• API user should be able to check routes with ports details
• Charter: Make sure there are no other ways for the routing API to betray us [Time Box: 1 Day] details
• Downloading droplets is not experimental in the api docs and link details
• TCP Routes are not experimental in the API docs details
• v3 Be consistent in capitalisation in V3 docs details
• v3 Can't create service instance when service broker was created with v2 details
• v3 Fix pagination link for that includes fields query param details
• v3 GA v3 service offerings details
• v3 GA v3 service plan visibility details
• v3 GA v3 service plans details
• v3 Respect catalog's plan_updateable property details
• v3 Service broker URL exposed when the broker errors during SI provision details
• v3 Update /v3 for services endpoints details
• v3 Validate request to update service instance name details
• v3 Validate request to update service instance plan details
• v3 Validate space/org quotas on plan update details
• v3 📘Docs: Clarify plan_updateable overrides details
• v3: Updating maintenance_info only (a.k.a. upgrading a SI) details
• v3: Update managed service instance using SYNC broker details
• Add available buildpacks to CF-for-k8s Store & Custom Builder details
• Create ADR for refactoring KubeClients/ CRD interactions details
• Create script to mass-produce resources in CC details
• Detect process_types from kpack-built image metadata details
• Emit app events in a way that is consumable by cf-for-k8s logging details
• Make "cloud_controller_ng", " cc_uploader", " cloud_controller_worker", " cc_deploymenet_updater" ," tps" , " cloud_controller_clock" and " blobstore'' jobs logs human readable based on property details
• Remove snyk details
• Unify all (experimental) tags in the docs details
• Usage events are not experimental in the v3 API docs and v3 link details

Cloud Controller Database Migrations

None

Pull Requests and Issues

• cloudfoundry/cli #1940: v7: set-org-role should not always default --origin to uaa details
• cloudfoundry/cloud_controller_ng #1567: [Feature Request]: Status in Revisions details
• cloudfoundry/cloud_controller_ng #1609: Add ADR for refactoring k8s clients details
• cloudfoundry/cloud_controller_ng #1625: Unusabl...

[DO NOT USE] Initial Release

DO NOT USE