Introduction¶

Most fields in the CRD are checked directly with kubebuilder validations, But some fields can be validated with a regular expression that is configurable through the PaasConfig:

Below snippet shows how validations can be configured for the complete set of vailable validations:

Example

apiVersion: cpet.belastingdienst.nl/v1alpha2
kind: PaasConfig
metadata:
  name: opr-paas-config
spec:
  validations:
    paas:
      # (v1.12) Validate name of Paas
      name: "^[a-z0-9-]*$"
      # (v1.12) Validate name of groups in paas
      groupName: "^[a-z0-9-]*$"
      # (v1.12) Validate name of namespaces in paas
      namespaceName: "^[a-z0-9-]*$"
      # (v1.12) Validate requestor field in paas
      requestor: "^[a-z0-9-]*$"
      # (v3.6) Allow quotas (by default all is allowed, by setting a regular expressions you can limit 
      # allowed quotas). Below example disallows limits.cpu (a.o.) and only allows the 4 types as stated.
      # This option has effect on:
      # - Quotas in a Paas resource
      # - Quotas in PaasConfig.spec.capabilities[*].quotas
      # - Quotas in PaasConfig.spec.maxAllowedSubmittedQuota.maxQuota
      allowedQuotas: "^(limits.memory|requests.cpu|requests.memory|requests.storage)$"
    paasConfig:
      # (v1.12) Validate name of capability in config
      capabilityName: "^[a-z0-9-]*$"
    paasNs:
      # (v1.12) Validate name of paasNs
      name: "^[a-z0-9-]*$"
...

Note

If only one of PaasConfig.spec.validations.paas.namespaceName, and PaasConfig.validations.paasNs.name is set, both PaasNs names and Paas.Spec.Namespaces are validated with the same validation rule.