Documentation
¶
Index ¶
Constants ¶
View Source
const ( // IdentityClusterName is the name of the logicalcluster that is backing the // current kcp workspace. Within each kcp workspace one can query for this // logicalcluster to resolve the workspace's path (e.g. "root:org1:teamx") // the logicalcluster name (e.g. "984235jkhwfowt45"). IdentityClusterName = "cluster" )
Variables ¶
This section is empty.
Functions ¶
func CreateAPIResourceSchema ¶ added in v0.3.0
func CreateAPIResourceSchema(crd *apiextensionsv1.CustomResourceDefinition, name string, agentName string) (*kcpapisv1alpha1.APIResourceSchema, error)
func GetAPIResourceSchemaName ¶ added in v0.3.0
func GetAPIResourceSchemaName(crd *apiextensionsv1.CustomResourceDefinition) string
GetAPIResourceSchemaName generates the name for the ARS in kcp. Note that kcp requires, just like CRDs, that ARS are named following a specific pattern.
Types ¶
type DynamicMultiClusterManager ¶ added in v0.5.0
type DynamicMultiClusterManager struct {
// contains filtered or unexported fields
}
DynamicMultiClusterManager (DMCM) is an extension to the regular multicluster manager. It's capable of starting new controllers at any time by keeping track of all engaged clusters (so that controllers that start later can be pre-seeded). Likewise it's possible to stop any of the controllers at any time.
The DMCM interface is goroutine-safe.
func NewDynamicMultiClusterManager ¶ added in v0.5.0
func NewDynamicMultiClusterManager(cfg *rest.Config, endpointSliceName string) (*DynamicMultiClusterManager, error)
func (*DynamicMultiClusterManager) GetManager ¶ added in v0.5.0
func (dmcm *DynamicMultiClusterManager) GetManager() mcmanager.Manager
func (*DynamicMultiClusterManager) Start ¶ added in v0.5.0
func (dmcm *DynamicMultiClusterManager) Start(ctx context.Context) error
func (*DynamicMultiClusterManager) StartController ¶ added in v0.5.0
func (dmcm *DynamicMultiClusterManager) StartController(ctx context.Context, log *zap.SugaredLogger, controller mcmanager.Runnable) error
StartController is like pre-seeding the new controller, adding it to the DMCM and then starting it in its own goroutine.
Source Files
Click to show internal directories.
Click to hide internal directories.