Available in:  EE

parameters

Schema version: 1

  • settings
    object
    • settings.gc
      object
      Garbage collection settings.
      • settings.gc.enabled
        boolean
        Enable periodic garbage collection.

        Default: false

      • settings.gc.schedule
        string
        Сron schedule for the garbage collector. Link for check: https://crontab.guru

        Examples:


        schedule: 0 20 * * 1
        
        schedule: 5 3 * * *
        
        schedule: 0 2 * * *
        
      • settings.gc.skipThreshold
        string
        The time interval within which the garbage collector task must start. If the task does not start within this interval, its execution is skipped until the next scheduled time. The feature is disabled by default. The minimum allowable value is 10 minutes. The following units of measurement are supported: h (hours), m (minutes), s (seconds).

        Pattern: ^(?:(\d+)h)?(?:(\d+)m)?(?:(\d+)s)?$

        Examples:


        skipThreshold: 20m
        
        skipThreshold: 1h
        
        skipThreshold: 1h20m30s
        
    • settings.https
      object

      What certificate type to use with the payload registry.

      This parameter completely overrides the global.modules.https settings.

      Examples:


      customCertificate:
        secretName: foobar
      mode: CustomCertificate
      
      certManager:
        clusterIssuerName: letsencrypt
      mode: CertManager
      
      • settings.https.certManager
        object

        Default: {}

        • settings.https.certManager.clusterIssuerName
          string

          What ClusterIssuer to use for the payload registry.

          Currently, letsencrypt, letsencrypt-staging, selfsigned are available. Also, you can define your own.

          Default: letsencrypt

      • settings.https.customCertificate
        object

        Default: {}

        • settings.https.customCertificate.secretName
          string

          The name of the secret in the d8-system namespace to use with the payload registry.

          This secret must have the kubernetes.io/tls format.

          Default: false

      • settings.https.mode
        string

        The HTTPS usage mode:

        • Disabled — in this mode, the payload registry can only be accessed over HTTP. Caution! This mode is not supported. HTTPS is required for the module to function properly. If HTTPS is disabled, the payload registry will be unavailable.
        • CertManager — the payload registry is accessed over HTTPS using a certificate obtained from a clusterIssuer specified in the certManager.clusterIssuerName parameter.
        • CustomCertificate — the payload registry is accessed over HTTPS using the certificate from the d8-system namespace.
        • OnlyInURI — the payload registry serves HTTP inside the cluster while an external HTTPS load balancer terminates TLS. All links will use the HTTPS scheme. The external load balancer must redirect HTTP to HTTPS.

        Allowed values: Disabled, CertManager, CustomCertificate, OnlyInURI

    • settings.persistence
      object
      Configuration parameters for PersistentVolumeClaim

      Default: {}

      • settings.persistence.accessModes
        array of strings

        Access modes for the PersistentVolumeClaim. This field is immutable, and to change it, a new PersistentVolumeClaim must be created.

        To change the parameter, go to the section “How to create a new PVC?”.

        Default: [ "ReadWriteOnce" ]

        Examples:


        accessModes:
        - ReadWriteOnce
        
        accessModes:
        - ReadWriteMany
        
        • settings.persistence.accessModes.Element of the array
          string

          Allowed values: ReadWriteOnce, ReadWriteMany

      • settings.persistence.name
        string
        The name of the PersistentVolumeClaim. Be careful: changing this field will result in the creation of a new PersistentVolumeClaim. The old PersistentVolumeClaim will remain in the namespace and must be manually deleted if it is no longer needed.

        Default: registry

        Length: 1..63

        Pattern: ^[a-z0-9]([-a-z0-9]*[a-z0-9])?$

        Examples:


        name: registry
        
        name: registry-hdd
        
        name: registry-network-ssd-2
        
      • settings.persistence.size
        string
        Disk size of the PersistentVolumeClaim. The minimum allowable value is 1Gi. Specify the desired disk size. You can increase the size later if necessary.

        Default: 10Gi

        Pattern: ^([+-]?[0-9.]+)([eEinumkKMGTP]*[-+]?[0-9]*)$

        Examples:


        size: 10Gi
        
        size: 1500Mi
        
      • settings.persistence.storageClass
        string

        The name of the StorageClass to be set when initializing the PersistentVolumeClaim. If this field is omitted, the StorageClass of the existing PersistentVolumeClaim will be used. If there is no PersistentVolumeClaim yet, either the global StorageClass or global.discovery.defaultStorageClass will be used. This field is immutable, and to change it, a new PersistentVolumeClaim must be created.

        To change the parameter, go to the section “How to create a new PVC?”.

        Examples:


        storageClass: ceph-ssd
        
        storageClass: network-hdd
        
        storageClass: network-ssd
        
    • settings.users
      object
      Configuration settings for user authorization within the payload registry.

      Default: {}

      Examples:


      username-1:
        passwordHash: $2y$05$WuwBasGDAgr.QCbGIjKJaep4dhxeai9gNZdmBnQXqpKly57oNutya
        projects:
        - access: FULL
          name: project-1
          subPath: path-*
        - access: READ
          name: project-1
          subPath: '*'
        - access: FULL
          name: project-2
          subPath: test/*
      
      username-2:
        passwordHash: $2y$05$WuwBasGDAgr.QCbGIjKJaep4dhxeai9gNZdmBnQXqpKly57oNutya