Administering TAS for Kubernetes
This topic describes how to administer Tanzu Application Service (TAS) for Kubernetes after initial installation.
Warning: Consult the Known Issues section for details on limitations of TAS for Kubernetes administration.
Developers create and manage their applications and service instances within spaces, and each of spaces belong to an org in the TAS installation. For more information about creating orgs and spaces and granting users access to them, see the Orgs, Spaces, Roles, and Permissions topic in the TAS documentation.
Quota plans are named sets of memory, service, and instance usage quotas that constrain the usage of organizations within a TAS installation. For more information, see the Creating and Modifying Quota Plans topic in the TAS documentation.
Developers typically need to connect their web applications running on TAS to dependencies such as data services. Service brokers give developers a self-service mechanism to provision these dependencies and to connect them to their applications. TAS administrators are responsible for registering these service brokers with the TAS installation and exposing their service plans to orgs and spaces. For more information, see the Managing Service Brokers topic in the TAS documentation.