validatingwebhook

Documentation

Index

• type RoleBindingRequestValidator
  • func (v RoleBindingRequestValidator) HandleValidate(w http.ResponseWriter, r *http.Request)
• type SSPRequestValidator
  • func (v SSPRequestValidator) HandleValidate(w http.ResponseWriter, r *http.Request)
• type SpaceBindingRequestValidator
  • func (v SpaceBindingRequestValidator) HandleValidate(w http.ResponseWriter, r *http.Request)

Types

type RoleBindingRequestValidator

type RoleBindingRequestValidator struct {
	Client runtimeClient.Client
}

func (RoleBindingRequestValidator) HandleValidate

func (v RoleBindingRequestValidator) HandleValidate(w http.ResponseWriter, r *http.Request)

type SSPRequestValidator

type SSPRequestValidator struct {
	Client runtimeClient.Client
}

The SSP resources is a CNV specific resource

func (SSPRequestValidator) HandleValidate

func (v SSPRequestValidator) HandleValidate(w http.ResponseWriter, r *http.Request)

type SpaceBindingRequestValidator

type SpaceBindingRequestValidator struct {
	Client runtimeClient.Client
}

SpaceBindingRequestValidator webhook validates SpaceBindingRequest CRs, Specifically it makes sure that once an SBR resource is created, the SpaceBindingRequest.Spec.MasterUserRecord field is not changed by the user. The reason for making SpaceBindingRequest.Spec.MasterUserRecord field immutable is that as of now the SpaceBinding resource name is composed as follows: <Space.Name>-checksum(<Space.Name>-<MasterUserRecord.Name>), thus changing it will trigger an updated of the SpaceBinding content but the name will still be based on the old MUR name. All the webhook configuration is available at member-operator/deploy/webhook/member-operator-webhook.yaml

func (SpaceBindingRequestValidator) HandleValidate

func (v SpaceBindingRequestValidator) HandleValidate(w http.ResponseWriter, r *http.Request)