Reference

CAPApplication spec

CAPApplication status

CAPApplicationVersion spec

CAPApplicationVersion status

CAPTenant spec

CAPTenant status

CAPTenantOperation spec

CAPTenantOperation status

Primary application domain will be used to generate a wildcard TLS certificate. In SAP Gardener managed clusters this is (usually) a subdomain of the cluster domain

Customer specific domains to serve application endpoints (optional)

Public ingress URL for the cluster Load Balancer

Labels used to identify the istio ingress-gateway component and its corresponding namespace. Usually {“app”:“istio-ingressgateway”,“istio”:“ingressgateway”}

Details of BTP Services

BTP subaccount subdomain

BTP subaccount Tenant ID

Domains used by the application

SAP BTP Global Account Identifier where services are entitles for the current application

Short name for the application (similar to BTP XSAPPNAME)

Provider subaccount where application services are created

SAP BTP Services consumed by the application

"Consistent"

CAPApplication has been reconciled and is now consistent

"Deleting"

Deletion has been triggered

"Error"

An error occurred during reconciliation

"Processing"

CAPApplication is being reconciled

(Members of GenericStatus are embedded into this type.)

State of CAPApplication

Hash representing last known application domains

The last time a full reconciliation was completed

"AllTenantsReady"

"LatestVersionReady"

Denotes to which CAPApplication the current version belongs

Semantic version

Registry secrets used to pull images of the application components

Information about the Workloads

Tenant Operations may be used to specify how jobs are sequenced for the different tenant operations

Content Jobs may be used to specify the sequence of content jobs when several jobs exist

"Deleting"

Deletion has been triggered

"Error"

An error occurred during reconciliation

"Processing"

CAPApplicationVersion is being processed

"Ready"

CAPApplicationVersion is now ready for use (dependent resources have been created)

(Members of GenericStatus are embedded into this type.)

State of CAPApplicationVersion

List of finished Content Jobs

Scope of the tenant lifecycle operation. One of ‘provisioning’, ‘deprovisioning’ or ‘upgrade’

(Members of BTPTenantIdentification are embedded into this type.)

BTP sub-account (tenant) for which request is created

Reference to CAPApplicationVersion for executing the operation

Steps (jobs) to be executed for the operation to complete

"Completed"

CAPTenantOperation steps completed

"Deleting"

CAPTenantOperation deletion has been triggered

"Failed"

CAPTenantOperation steps have failed

"Processing"

CAPTenantOperation is being processed

(Members of GenericStatus are embedded into this type.)

State of CAPTenantOperation

Current step being processed from the sequence of specified steps

Name of the job being executed for the current step

Name of the workload from the referenced CAPApplicationVersion

Type of job. One of ‘TenantOperation’ or ‘CustomTenantOperation’

Indicates whether the operation can continue in case of step failure. Relevant only for type ‘CustomTenantOperation’

"deprovisioning"

Deprovision tenant

"provisioning"

Provision tenant

"upgrade"

Upgrade tenant

Denotes to which CAPApplication the current tenant belongs

(Members of BTPTenantIdentification are embedded into this type.)

Details of consumer sub-account subscribing to the application

Semver that is used to determine the relevant CAPApplicationVersion that a CAPTenant can be upgraded to (i.e. if it is not already on that version)

Denotes whether a CAPTenant can be upgraded. One of (‘always’, ‘never’)

"Deleting"

Deletion has been triggered

"Provisioning"

Tenant is being provisioned

"ProvisioningError"

Tenant provisioning ended in error

"Ready"

Tenant has been provisioned/upgraded and is now ready for use

"UpgradeError"

Tenant upgrade failed

"Upgrading"

Tenant is being upgraded

(Members of GenericStatus are embedded into this type.)

State of CAPTenant

Specifies the current version of the tenant after provisioning or upgrade

Previous versions of the tenant (first to last)

The last time a full reconciliation was completed

Image info for the container

Pull policy for the container image

Entrypoint array for the container

Environment Config for the Container

Volume Configuration for the Pod

Volume Mount Configuration for the Container

Name of the ServiceAccount to use to run the Pod

Resources

SecurityContext for the Container

SecurityContext for the Pod

The name of the node to which the Pod should be assigned to. See: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodename

The label selectors using which node for the Pod would be determined. See: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector

Priority class name mapping used to prioritize and schedule the Pod. See: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass

Affinity/anti-affinity used to provide more constraints for node selection. See: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity

Tolerations used to schedule the Pod. See: https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/

The Topology spread constraints used to control how Pods are spread across regions, zones, nodes etc. See: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#pod-topology-spread-constraints

(Members of CommonDetails are embedded into this type.)

Type of the Deployment

Number of replicas

Port configuration

Liveness probe

Readiness probe

"Additional"

Additional deployment type

"CAP"

CAP backend server deployment type

"Router"

Application router deployment type

Observed generation of the resource where this status was identified

State expressed as conditions

(Members of CommonDetails are embedded into this type.)

Type of Job

Specifies the number of retries before marking this job failed.

Specifies the time after which the job may be cleaned up.

"Content"

job for deploying content or configuration to (BTP) services

"CustomTenantOperation"

job for custom tenant operation e.g. pre/post hooks for a tenant operation

"TenantOperation"

job for tenant operation e.g. deploying relevant data to a tenant

"Application"

Expose the port for the current application versions pod(s) scope

"Cluster"

Expose the port for any pod(s) in the overall cluster scope

App protocol used by the service port

Name of the service port

Network Policy of the service port

The port number used for container and the corresponding service (if any)

Destination name which may be used by the Router deployment to reach this backend service

A unique name of service based on usage in the app (this may be the name of the instance or binding)

Secret containing service access credentials

Type of service

"Ready"

Reference to a specified workload of type ‘TenantOperation’ or ‘CustomTenantOperation’

Indicates whether to proceed with remaining operation steps in case of failure. Relevant only for ‘CustomTenantOperation’

Tenant provisioning steps

Tenant upgrade steps

Tenant deprovisioning steps

"always"

Always (default)

"never"

Never

Name of the workload

List of BTP services consumed by the current application component workload. These services must be defined in the corresponding CAPApplication.

Custom labels for the current workload

Annotations for the current workload, in case of Deployments this also get copied over to any Service that may be created

Definition of a deployment

Definition of a job