- ServiceMeshControlPlane
-
ServiceMeshControlPlane is the Schema for the controlplanes API
- ServiceMeshControlPlane
-
ServiceMeshControlPlane represents a deployment of the service mesh control plane. The control plane components are deployed in the namespace in which the ServiceMeshControlPlane resides. The configuration options for the components that comprise the control plane are specified in this object.
- ServiceMeshExtension
-
ServiceMeshExtension is the Schema for the servicemeshextensions API
- ServiceMeshMember
-
A ServiceMeshMember object marks the namespace in which it lives as a member of the Service Mesh Control Plane referenced in the object. The ServiceMeshMember object should be created in each application namespace that must be part of the service mesh and must be named "default". When the ServiceMeshMember object is created, it causes the namespace to be added to the ServiceMeshMemberRoll within the namespace of the ServiceMeshControlPlane object the ServiceMeshMember references. To reference a ServiceMeshControlPlane, the user creating the ServiceMeshMember object must have the "use" permission on the referenced ServiceMeshControlPlane object. This permission is given via the mesh-users RoleBinding (and mesh-user Role) in the namespace of the referenced ServiceMeshControlPlane object.
- ServiceMeshMemberRoll
-
The ServiceMeshMemberRoll object configures which namespaces belong to a service mesh. Only namespaces listed in the ServiceMeshMemberRoll will be affected by the control plane. Any number of namespaces can be added, but a namespace may not exist in more than one service mesh. The ServiceMeshMemberRoll object must be created in the same namespace as the ServiceMeshControlPlane object and must be named "default".
- ServiceMeshExtension
-
ServiceMeshExtension is the Schema for the servicemeshextensions API
- ExportedServiceSet
-
ExportedServiceSet is the Schema for configuring exported services. It must be created in the same namespace as the control plane. The name of the ExportedServiceSet resource must match the name of a ServiceMeshPeer resource defining the remote mesh to which the services will be exported. This implies there will be at most one ExportedServiceSet resource per peer and control plane.
- ImportedServiceSet
-
ImportedServiceSet is the Schema for configuring imported services. It must be created in the same namespace as the control plane. The name of the ImportedServiceSet resource must match the name of a ServiceMeshPeer resource defining the remote mesh from which the services will be imported. This implies there will be at most one ImportedServiceSet resource per peer and control plane.
- ServiceMeshPeer
-
ServiceMeshPeer is the Schema for joining two meshes together. The resource name will be used to identify the 'cluster' to which imported services belong.