Tenant

The differences between TSB and Tetrate Istio Subscription Plus (TIS+)

Tetrate Istio Subscription Plus (TIS+) utilizes many of the same components as the Tetrate Service Bridge(TSB) product but has the several distinctions.

Tenant is a self-contained entity within an organization in the Istio Subscription Plus object hierarchy. Tenants can be business units, organization units, or any logical grouping that matches a corporate structure.

The following example creates a tenant named mycompany in an organization named myorg.

apiVersion: api.tsb.tetrate.io/v2
kind: Tenant
metadata:
  organization: tis+
  name: mycompany

Tenant

Tenant is a self-contained entity within an organization in the Istio Subscription Plus hierarchy.

Field	Description	Validation Rule
securityDomain	string Security domains can be used to group different resources under the same security domain. Although security domain is not resource itself currently, it follows a fqn format organizations/myorg/securitydomains/mysecuritydomain, and a child cannot override any ancestor's security domain. Once a security domain is assigned to a Tenant, all the children resources will belong to that security domain in the same way a Workspace belongs to a Tenant, a Workspace will also belong to the security domain assigned to the Tenant. Security domains can also be used to define Security settings Authorization rules in which you can allow or deny request from or to a security domain.	–
deletionProtectionEnabled	bool When set, prevents the resource from being deleted. In order to delete the resource this property needs to be set to false first.	–
profiles	List of string List of profiles attached to the tenant to be used to propagate default and mandatory configurations down to the children.	–
configGenerationMetadata	tetrateio.api.tsb.types.v2.ConfigGenerationMetadata Default metadata values that will be propagated to the children Istio generated configurations. When using YAML APIs like tctl or gitops, put them into the metadata.labels or metadata.annotations instead. This field is only necessary when using gRPC APIs directly.	–