The Deckhouse Kubernetes Platform installs CRDs but does not remove them when a module is disabled. If you no longer need the created CRDs, delete them.

VCDInstanceClass

Scope: Cluster
Version: v1

Parameters of a group of VCD VirtualMachines used by cluster-api-controller-manager (the cloud-provider-vcd module).

  • spec
    object

    Required value

    • spec.additionalMetadata
      object

      Custom string key-value pairs to be stored in the Metadata of every node VM, useful for organizing and categorizing your virtualization inventory.

      The properties in this field will be merged with the existing metadata stored in the metadata field at the root of the VCDProviderClusterConfiguration spec. This field will take precedence over the existing metadata in cases of duplicate keys.

      Warning. Changing the additionalMetadata will cause the recreation of CloudEphemeral NodeGroups referring the VCDInstanceClass.

    • spec.affinityRule
      object

      Specifies the affinity rule applied only to virtual machines of node groups referencing this instance class within the cluster. Affinity rules determine how nodes are scheduled in relation to each other at the hypervisor level, which can help improve fault tolerance, and control the distribution of workloads. If not specified, no affinity rule will be applied by default.

      • spec.affinityRule.polarity
        string

        Required value

        The polarity of the affinity rule. Must be either Affinity or AntiAffinity. Affinity means that nodes should be placed on the same host, while AntiAffinity means they should be placed on different hosts.

        Allowed values: Affinity, AntiAffinity

      • spec.affinityRule.required
        boolean

        Indicates whether the affinity rule is mandatory (true) or only preferred (false). If set to true, the rule must be enforced; if false, the rule is applied if possible but not strictly required.

        Default: false

    • spec.mainNetwork
      string

      Path to the network that VirtualMachines’ primary NICs will connect to (default gateway).

      Example:

      mainNetwork: internal
    • spec.placementPolicy
      string

      PlacementPolicy is the placement policy to be used on this machine. If no placement policy is specified, default placement policy will be used to create the nodes.

      Example:

      placementPolicy: Hypervisor1
    • spec.rootDiskSizeGb
      integer

      root disk size in gigabytes.

      Default: 20

      Example:

      rootDiskSizeGb: 20
    • spec.sizingPolicy
      string

      SizingPolicy is the sizing policy to be used on this machine. If no sizing policy is specified, default sizing policy will be used to create the nodes.

      Example:

      sizingPolicy: 4Cpu8Memory
    • spec.storageProfile
      string

      Required value

      StorageProfile is the storage profile to be used on this machine.

      Example:

      storageProfile: ssd
    • spec.template
      string

      Required value

      Path of the template OVA that is to be used. Consists of organization (optional), catalog, template name or template identifier. If a shared catalog is used, the organization name must be specified (it may differ from the value of provider.organization).

      If you have templates with the same name in multiple catalogs with the same name, you should specify the identifier of the template.

      You can find the template identifier in the URL when you open the template in the vCD UI. For example, if the URL is https://vcd.example.com/tenant/MyOrg/libraries/catalogs/1032506a-4555-43e1-8589-77b0c0522c75/catalog-vapp-templates/5438c9f2-7e59-4eb3-b37c-cbd7f3e710c7/general, then the template identifier is 5438c9f2-7e59-4eb3-b37c-cbd7f3e710c7.

      Examples:

      template: Linux/ubuntu2204-cloud-ova

      template: MyOrg/Linux/ubuntu2204-cloud-ova

      template: Linux/5438c9f2-7e59-4eb3-b37c-cbd7f3e710c7

      template: MyOrg/Linux/5438c9f2-7e59-4eb3-b37c-cbd7f3e710c7