Scope of Support - Application Service Adapter
Article ID: 298444
Updated On:
Products
Issue/Introduction
This document is not a legal document, see the disclaimer at the bottom. If you are looking for these official documents, please see Support Offerings , Support Terms and Conditions , and Support Lifecycle .
Environment
Resolution
In Scope
Application Service Adapter for Tanzu Application Platform is available on Broadcom downloads:
| The following items are covered by VMware Support | In Scope |
|---|---|
| Installation / Upgrade of TAS Adapter | Yes[1] |
| Usage & Configuration as per Product Documentation | Yes |
| Performance issues | Yes |
| Bug reporting | Yes |
| Bug Fixes | Yes[2] |
| Debugging TAS Adapter component failures (Crash dumps, logs, etc) | Yes |
Out of Scope
The following items are examples of tasks that are not covered by VMware Support:
VMware Maintenance and Premium Support Programs — Terms and Conditions
| The following items are not covered by VMware Support | In Scope |
|---|---|
| Third Party or community extensions | No |
| Bulk migration of applications (contact Professional Services) | No |
| Application re-platforming (contact Professional Services) | No |
| Application issues | No |
[1] - Installation / Initial setup / Upgrade of TAS Adapter is a customer activity or a paid services engagement.
[2] - Bug fixes are prioritized by Engineering with input from Support and our customers. There is no guarantee of an immediate fix. Support retains the right to close out support tickets if a fix is not immediate.
[3] - VMware Support will provide best-effort support for beta/experiment features that are shipped in a generally available product. The goal in this case is to find and report bugs so that the feature works correctly when it is generally available. A fix for any bugs uncovered may not be available until the feature is generally available. Production and Severity 1 support is not available for beta/experimental features.
TAS Adapter Components
The TAS Adapter package installs several Kubernetes Deployments and custom resources. The core of TAS Adapter is provided by the open source Cloud Foundry Korifi project and it is accompanied by several proprietary extensions that integrate it more deeply with Tanzu Application Platform.
For more details on the architecture, please refer to our Technical Architecture docs.
Custom Resources
The following custom resources are installed by the TAS Adapter package and are fully managed by the product. If there is a problem with the TAS Adapter, inspecting these resources can be helpful.
| Name | API Version | Kind | Description |
|---|---|---|---|
| cfapps | korifi.cloudfoundry.org/v1alpha1 | CFApp | The high-level Cloud Foundry "App" resource |
| cfpackages | korifi.cloudfoundry.org/v1alpha1 | CFPackage | The Cloud Foundry "Package" resource representing an app's source code |
| cfbuilds | korifi.cloudfoundry.org/v1alpha1 | CFBuild | The Cloud Foundry "Build" resource that initiates app staging |
| cfprocesses | korifi.cloudfoundry.org/v1alpha1 | CFProcess | The Cloud Foundry "Build" resource that represents the runnable config for an app |
| cforgs | korifi.cloudfoundry.org/v1alpha1 | CFOrg | The Cloud Foundry "Org" resource. It is backed by a Kubernetes namespace that contains CFSpace resources. |
| cfspaces | korifi.cloudfoundry.org/v1alpha1 | CFSpace | The Cloud Foundry "Space" resource. It is backed by a Kubernetes namespace that contains app build/run Pods. |
| cfdomains | korifi.cloudfoundry.org/v1alpha1 | CFDomain | The Cloud Foundry "Domain" resource. It represents a domain that routes can be created for. |
| cfroutes | korifi.cloudfoundry.org/v1alpha1 | CFRoute | The Cloud Foundry "Route" resource. It configures the routing system (Contour) for app ingress routing. |
| cfservicebindings | korifi.cloudfoundry.org/v1alpha1 | CFServiceBinding | The Cloud Foundry "Service Binding" resource. It binds a service instance to an app. |
| cfserviceinstances | korifi.cloudfoundry.org/v1alpha1 | CFServiceInstance | The Cloud Foundry "Service Instance" resource. Currently only user-provided service instances are supported. |
| appworkloads | korifi.cloudfoundry.org/v1alpha1 | AppWorkload | An extension point resource that serves as an interface for alternative app runner implementations. |
| buildworkloads | korifi.cloudfoundry.org/v1alpha1 |
BuildWorkload |
An extension point resource that serves as an interface for alternative app builder (staging) implementations. |
| taskworkloads | korifi.cloudfoundry.org/v1alpha1 | TaskWorkload | An extension point resource that serves as an interface for alternative task runner implementations. |
Deployments
The TAS Adapter installation creates the following deployments, which are supported by the DAP Workload Portability program. If there is a problem with the TAS Adapter, collecting logs from these deployments is a good place to start.
| Name | Default Namespace | Description |
|---|---|---|
| korifi-api-deployment | tas-adapter-system | CF API translation layer |
| korifi-controllers-controller-manager | tas-adapter-system | Controller for Korifi custom resources and hosts mutating/validating admission webhooks |
| korifi-kpack-build-controller-manager | tas-adapter-system | Controller for building (staging) apps using Tanzu Build Service (default builder) |
| korifi-statefulset-runner-controller-manager | tas-adapter-system | Controller for running apps as Kubernetes StatefulSets (default runner) |
| korifi-job-task-runner-controller-manager | tas-adapter-system | Controller for running CF tasks as Kubernetes Jobs (default task runner) |
| cartographer-builder-runner-controller-manager | tas-adapter-system | Experimental controller integrating with TAP Supply Chain Choreographer (Cartographer) Supply Chains for building/running apps |
| tas-adapter-telemetry-informer | tas-adapter-system | Collects and submits telemetry data using the Tanzu Telemetry SDK |
Webhook Configuration
TAS Adapter registers the following mutating/validating webhooks, which it uses for validating its resources and normalizing them.
| Name | Resources Managed |
|---|---|
| korifi-controllers-validating-webhook-configuration | cfapps, cfdomains, cfroutes, cfserviceinstances |
| korifi-controllers-mutating-webhook-configuration | cfapps, cfpackages, cfbuilds, cfprocesses, cfroutes |
V3 Cloud Foundry API
TAS Adapter implements a limited subset of the CF V3 API, primarily oriented around supporting the CF CLI's "cf push" workflow.
Supported endpoints are listed here.
Note on External Integration Points
The TAS Adapter interfaces with TAP components such as Contour and Tanzu Build Service. The DAP Workload Portability program is responsible for its usage of these components and the custom resources it manages to integrate with them but is not responsible for the components themselves. For example, if an app is not routable because the CFRoute and Contour HTTPProxy that the TAS Adapter produces is invalid, that is something we can debug and help with. However, if an app is unreachable because of a bug with Contour or the networking on their cluster itself we may be less equipped to help and will need to direct support to someone with more expertise. Likewise for components like Tanzu Build Service or Supply Chain Choreographer.
Here are some example resources that represent this kind of integration:
| Example | Kind | APIVersion | Description |
|---|---|---|---|
| cf-route-6fb664cf-77c8-407a-8724-32066a7606c4 | HTTPProxy | projectcontour.io/v1 | HTTP Proxy for routing traffic to CF Apps |
| df916d07-9d50-402c-a7aa-869ea6792468 | Image | kpack.io/v1alpha2 | Stages CF App builds via Tanzu Build Service (kpack) |
Feedback
