operations

Documentation

Index

• func NewDispatchRevokeCredentialsController(clock utilsclock.PassiveClock, ...) controllerutils.Controller
• func NewOperationRevokeCredentialsPollController(clock utilsclock.PassiveClock, ...) controllerutils.Controller

Functions

func NewDispatchRevokeCredentialsController

func NewDispatchRevokeCredentialsController(
	clock utilsclock.PassiveClock,
	resourcesDBClient corecosmosstorage.ResourcesDBClient,
	clusterLister corelisters.ClusterLister,
	activeOperationInformer cache.SharedIndexInformer,
) controllerutils.Controller

NewDispatchRevokeCredentialsController returns a Controller that handles the first step of a RevokeCredentials operation: it creates a single SystemAdminCredentialRevocation document nested under the cluster, records its resource ID on SystemAdminCredentialRevocation, and moves the operation to Deleting. The actual revocation work (marking credential requests for deletion, driving the CertificateRevocationRequest desires, and tearing them down) is performed by the dedicated SystemAdminCredentialRevocation controllers. The operation completes once the revocation document is gone.

Operation documents relevant to this controller will have the following values:

ResourceType: Microsoft.RedHatOpenShift/hcpOpenShiftClusters
     Request: OperationRequestSystemAdminCredentialRevocation ("RevokeCredentials")
      Status: Accepted
  SystemAdminCredentialRevocation: nil

func NewOperationRevokeCredentialsPollController

func NewOperationRevokeCredentialsPollController(
	clock utilsclock.PassiveClock,
	resourcesDBClient corecosmosstorage.ResourcesDBClient,
	clusterLister corelisters.ClusterLister,
	notificationClient *http.Client,
	activeOperationInformer cache.SharedIndexInformer,
) controllerutils.Controller

NewOperationRevokeCredentialsPollController returns a Controller that follows a RevokeCredentials operation to completion. The dispatch controller creates a SystemAdminCredentialRevocation document, records it on the operation's SystemAdminCredentialRevocation, and moves the operation to Deleting. The dedicated revocation controllers then drive the revocation and delete that document when finished. This poll controller simply waits for the document to disappear; once it is gone it clears the cluster's revoke sentinel and marks the operation Succeeded.