chore: generate vCluster partials for main version based on values.schema.json in vCluster v0.23.0-rc.5

configsrc/vcluster/main/default_values.yaml

@@ -57,8 +57,8 @@ sync:
       enabled: true
     configMaps:
       enabled: false
-      selector:
-        mappings: {}
+      mappings:
+        byName: {}
     csiDrivers:
       enabled: auto
     csiNodes:
@@ -82,8 +82,8 @@ sync:
         labels: {}
     secrets:
       enabled: false
-      selector:
-        mappings: {}
+      mappings:
+        byName: {}
     volumeSnapshotClasses:
       enabled: false
 
@@ -397,6 +397,8 @@ controlPlane:
     globalMetadata:
       annotations: {}
 
+    reuseNamespace: false
+
 integrations:
   metricsServer:
     enabled: false
@@ -574,5 +576,3 @@ experimental:
 
 telemetry:
   enabled: true
-
-reuseNamespace: false

configsrc/vcluster/main/vcluster.schema.json

@@ -268,6 +268,10 @@
         "globalMetadata": {
           "$ref": "#/$defs/ControlPlaneGlobalMetadata",
           "description": "GlobalMetadata is metadata that will be added to all resources deployed by Helm."
+        },
+        "reuseNamespace": {
+          "type": "boolean",
+          "description": "ReuseNamespace allows reusing the same namespace to create multiple vClusters.\nThis flag is deprecated, as this scenario will be removed entirely in upcoming releases."
         }
       },
       "additionalProperties": false,
@@ -1168,9 +1172,9 @@
           "type": "array",
           "description": "Patches patch the resource according to the provided specification."
         },
-        "selector": {
-          "$ref": "#/$defs/FromHostSelector",
-          "description": "Selector for Namespace and Object"
+        "mappings": {
+          "$ref": "#/$defs/FromHostMappings",
+          "description": "Mappings for Namespace and Object"
         }
       },
       "additionalProperties": false,
@@ -1848,14 +1852,14 @@
       "additionalProperties": false,
       "type": "object"
     },
-    "FromHostSelector": {
+    "FromHostMappings": {
       "properties": {
-        "mappings": {
+        "byName": {
           "additionalProperties": {
             "type": "string"
           },
           "type": "object",
-          "description": "Mappings is a map of host-object-namespace/host-object-name: virtual-object-namespace/virtual-object-name.\nThere are several wildcards supported:\n1. To match all objects in host namespace and sync them to different namespace in vCluster:\nmappings:\n  \"foo/*\": \"foo-in-virtual/*\"\n2. To match specific object in the host namespace and sync it to the same namespace with the same name:\nmappings:\n  \"foo/my-object\": \"foo/my-object\"\n3. To match specific object in the host namespace and sync it to the same namespace with different name:\nmappings:\n  \"foo/my-object\": \"foo/my-virtual-object\"\n4. To match all objects in the vCluster host namespace and sync them to a different namespace in vCluster:\nmappings:\n  \"\": \"my-virtual-namespace/*\"\n5. To match specific objects in the vCluster host namespace and sync them to a different namespace in vCluster:\nmappings:\n  \"/my-object\": \"my-virtual-namespace/my-object\""
+          "description": "ByName is a map of host-object-namespace/host-object-name: virtual-object-namespace/virtual-object-name.\nThere are several wildcards supported:\n1. To match all objects in host namespace and sync them to different namespace in vCluster:\nbyName:\n  \"foo/*\": \"foo-in-virtual/*\"\n2. To match specific object in the host namespace and sync it to the same namespace with the same name:\nbyName:\n  \"foo/my-object\": \"foo/my-object\"\n3. To match specific object in the host namespace and sync it to the same namespace with different name:\nbyName:\n  \"foo/my-object\": \"foo/my-virtual-object\"\n4. To match all objects in the vCluster host namespace and sync them to a different namespace in vCluster:\nbyName:\n  \"\": \"my-virtual-namespace/*\"\n5. To match specific objects in the vCluster host namespace and sync them to a different namespace in vCluster:\nbyName:\n  \"/my-object\": \"my-virtual-namespace/my-object\""
         }
       },
       "additionalProperties": false,
@@ -3249,9 +3253,9 @@
           "type": "array",
           "description": "Patches patch the resource according to the provided specification."
         },
-        "selector": {
-          "$ref": "#/$defs/FromHostSelector",
-          "description": "Selector for Namespace and Object"
+        "mappings": {
+          "$ref": "#/$defs/FromHostMappings",
+          "description": "Mappings for Namespace and Object"
         }
       },
       "additionalProperties": false,
@@ -3878,10 +3882,6 @@
         "$ref": "#/$defs/Plugin"
       },
       "description": "Plugin specifies which vCluster plugins to enable. Use \"plugins\" instead. Do not use this option anymore."
-    },
-    "reuseNamespace": {
-      "type": "boolean",
-      "description": "ReuseNamespace allows reusing the same namespace to create multiple vClusters.\nThis flag is deprecated, as this scenario will be removed entirely in upcoming releases."
     }
   },
   "additionalProperties": false,

vcluster/_partials/config/controlPlane.mdx

@@ -4110,6 +4110,22 @@ Annotations are extra annotations for this resource.
 </details>
 
 
+</details>
+
+
+
+<details className="config-field" data-expandable="false" open>
+<summary>
+
+#### `reuseNamespace` <span className="config-field-required" data-required="false">required</span> <span className="config-field-type">boolean</span> <span className="config-field-default">false</span> <span className="config-field-enum"></span> <span data-pro="false" className="config-field-pro">pro</span> {#controlPlane-advanced-reuseNamespace}
+
+ReuseNamespace allows reusing the same namespace to create multiple vClusters.
+This flag is deprecated, as this scenario will be removed entirely in upcoming releases.
+
+</summary>
+
+
+
 </details>
 
 

vcluster/_partials/config/controlPlane/advanced.mdx

@@ -338,6 +338,22 @@ Annotations are extra annotations for this resource.
 </details>
 
 
+</details>
+
+
+
+<details className="config-field" data-expandable="false" open>
+<summary>
+
+### `reuseNamespace` <span className="config-field-required" data-required="false">required</span> <span className="config-field-type">boolean</span> <span className="config-field-default">false</span> <span className="config-field-enum"></span> <span data-pro="false" className="config-field-pro">pro</span> {#advanced-reuseNamespace}
+
+ReuseNamespace allows reusing the same namespace to create multiple vClusters.
+This flag is deprecated, as this scenario will be removed entirely in upcoming releases.
+
+</summary>
+
+
+
 </details>
 
 

vcluster/_partials/config/sync.mdx

@@ -5896,9 +5896,9 @@ Labels treats the path value as a labels selector.
 <details className="config-field" data-expandable="true">
 <summary>
 
-##### `selector` <span className="config-field-required" data-required="false">required</span> <span className="config-field-type">object</span> <span className="config-field-default"></span> <span className="config-field-enum"></span> <span data-pro="false" className="config-field-pro">pro</span> {#sync-fromHost-customResources-selector}
+##### `mappings` <span className="config-field-required" data-required="false">required</span> <span className="config-field-type">object</span> <span className="config-field-default"></span> <span className="config-field-enum"></span> <span data-pro="false" className="config-field-pro">pro</span> {#sync-fromHost-customResources-mappings}
 
-Selector for Namespace and Object
+Mappings for Namespace and Object
 
 </summary>
 
@@ -5908,24 +5908,24 @@ Selector for Namespace and Object
 <details className="config-field" data-expandable="false" open>
 <summary>
 
-##### `mappings` <span className="config-field-required" data-required="false">required</span> <span className="config-field-type">object</span> <span className="config-field-default"></span> <span className="config-field-enum"></span> <span data-pro="false" className="config-field-pro">pro</span> {#sync-fromHost-customResources-selector-mappings}
+##### `byName` <span className="config-field-required" data-required="false">required</span> <span className="config-field-type">object</span> <span className="config-field-default"></span> <span className="config-field-enum"></span> <span data-pro="false" className="config-field-pro">pro</span> {#sync-fromHost-customResources-mappings-byName}
 
-Mappings is a map of host-object-namespace/host-object-name: virtual-object-namespace/virtual-object-name.
+ByName is a map of host-object-namespace/host-object-name: virtual-object-namespace/virtual-object-name.
 There are several wildcards supported:
 1. To match all objects in host namespace and sync them to different namespace in vCluster:
-mappings:
+byName:
   "foo/*": "foo-in-virtual/*"
 2. To match specific object in the host namespace and sync it to the same namespace with the same name:
-mappings:
+byName:
   "foo/my-object": "foo/my-object"
 3. To match specific object in the host namespace and sync it to the same namespace with different name:
-mappings:
+byName:
   "foo/my-object": "foo/my-virtual-object"
 4. To match all objects in the vCluster host namespace and sync them to a different namespace in vCluster:
-mappings:
+byName:
   "": "my-virtual-namespace/*"
 5. To match specific objects in the vCluster host namespace and sync them to a different namespace in vCluster:
-mappings:
+byName:
   "/my-object": "my-virtual-namespace/my-object"
 
 </summary>
@@ -6368,9 +6368,9 @@ Labels treats the path value as a labels selector.
 <details className="config-field" data-expandable="true">
 <summary>
 
-##### `selector` <span className="config-field-required" data-required="false">required</span> <span className="config-field-type">object</span> <span className="config-field-default"></span> <span className="config-field-enum"></span> <span data-pro="false" className="config-field-pro">pro</span> {#sync-fromHost-configMaps-selector}
+##### `mappings` <span className="config-field-required" data-required="false">required</span> <span className="config-field-type">object</span> <span className="config-field-default"></span> <span className="config-field-enum"></span> <span data-pro="false" className="config-field-pro">pro</span> {#sync-fromHost-configMaps-mappings}
 
-Selector for Namespace and Object
+Mappings for Namespace and Object
 
 </summary>
 
@@ -6380,24 +6380,24 @@ Selector for Namespace and Object
 <details className="config-field" data-expandable="false" open>
 <summary>
 
-##### `mappings` <span className="config-field-required" data-required="false">required</span> <span className="config-field-type">object</span> <span className="config-field-default">&#123;&#125;</span> <span className="config-field-enum"></span> <span data-pro="false" className="config-field-pro">pro</span> {#sync-fromHost-configMaps-selector-mappings}
+##### `byName` <span className="config-field-required" data-required="false">required</span> <span className="config-field-type">object</span> <span className="config-field-default">&#123;&#125;</span> <span className="config-field-enum"></span> <span data-pro="false" className="config-field-pro">pro</span> {#sync-fromHost-configMaps-mappings-byName}
 
-Mappings is a map of host-object-namespace/host-object-name: virtual-object-namespace/virtual-object-name.
+ByName is a map of host-object-namespace/host-object-name: virtual-object-namespace/virtual-object-name.
 There are several wildcards supported:
 1. To match all objects in host namespace and sync them to different namespace in vCluster:
-mappings:
+byName:
   "foo/*": "foo-in-virtual/*"
 2. To match specific object in the host namespace and sync it to the same namespace with the same name:
-mappings:
+byName:
   "foo/my-object": "foo/my-object"
 3. To match specific object in the host namespace and sync it to the same namespace with different name:
-mappings:
+byName:
   "foo/my-object": "foo/my-virtual-object"
 4. To match all objects in the vCluster host namespace and sync them to a different namespace in vCluster:
-mappings:
+byName:
   "": "my-virtual-namespace/*"
 5. To match specific objects in the vCluster host namespace and sync them to a different namespace in vCluster:
-mappings:
+byName:
   "/my-object": "my-virtual-namespace/my-object"
 
 </summary>
@@ -6627,9 +6627,9 @@ Labels treats the path value as a labels selector.
 <details className="config-field" data-expandable="true">
 <summary>
 
-##### `selector` <span className="config-field-required" data-required="false">required</span> <span className="config-field-type">object</span> <span className="config-field-default"></span> <span className="config-field-enum"></span> <span data-pro="false" className="config-field-pro">pro</span> {#sync-fromHost-secrets-selector}
+##### `mappings` <span className="config-field-required" data-required="false">required</span> <span className="config-field-type">object</span> <span className="config-field-default"></span> <span className="config-field-enum"></span> <span data-pro="false" className="config-field-pro">pro</span> {#sync-fromHost-secrets-mappings}
 
-Selector for Namespace and Object
+Mappings for Namespace and Object
 
 </summary>
 
@@ -6639,24 +6639,24 @@ Selector for Namespace and Object
 <details className="config-field" data-expandable="false" open>
 <summary>
 
-##### `mappings` <span className="config-field-required" data-required="false">required</span> <span className="config-field-type">object</span> <span className="config-field-default">&#123;&#125;</span> <span className="config-field-enum"></span> <span data-pro="false" className="config-field-pro">pro</span> {#sync-fromHost-secrets-selector-mappings}
+##### `byName` <span className="config-field-required" data-required="false">required</span> <span className="config-field-type">object</span> <span className="config-field-default">&#123;&#125;</span> <span className="config-field-enum"></span> <span data-pro="false" className="config-field-pro">pro</span> {#sync-fromHost-secrets-mappings-byName}
 
-Mappings is a map of host-object-namespace/host-object-name: virtual-object-namespace/virtual-object-name.
+ByName is a map of host-object-namespace/host-object-name: virtual-object-namespace/virtual-object-name.
 There are several wildcards supported:
 1. To match all objects in host namespace and sync them to different namespace in vCluster:
-mappings:
+byName:
   "foo/*": "foo-in-virtual/*"
 2. To match specific object in the host namespace and sync it to the same namespace with the same name:
-mappings:
+byName:
   "foo/my-object": "foo/my-object"
 3. To match specific object in the host namespace and sync it to the same namespace with different name:
-mappings:
+byName:
   "foo/my-object": "foo/my-virtual-object"
 4. To match all objects in the vCluster host namespace and sync them to a different namespace in vCluster:
-mappings:
+byName:
   "": "my-virtual-namespace/*"
 5. To match specific objects in the vCluster host namespace and sync them to a different namespace in vCluster:
-mappings:
+byName:
   "/my-object": "my-virtual-namespace/my-object"
 
 </summary>