Virtual Cluster Template
Virtual Cluster templates can be used to create virtual clusters that have already certain applications deployed inside them or other predefined configuration applied. They are a powerful tool to create new predefined environments on demand.
Example Virtual Cluster Template
An example Virtual Cluster Template:
apiVersion: management.loft.sh/v1
kind: VirtualClusterTemplate
metadata:
creationTimestamp: null
name: my-virtual-cluster-template
spec:
access:
- users:
- '*'
verbs:
- get
description: This virtual cluster template deploys an isolated virtual cluster
displayName: Isolated Virtual Cluster Template
template:
accessPoint:
ingress: {}
helmRelease:
chart: {}
values: |-
# Below you can configure the virtual cluster
isolation:
enabled: true
# Checkout https://vcluster.com/docs for more config options
instanceTemplate:
metadata: {}
metadata: {}
pro: {}
spaceTemplate:
metadata: {}
status: {}
Virtual Cluster Template Reference
kind
required string pro
Kind is a string value representing the REST resource this object represents.
Servers may infer this from the endpoint the client submits requests to.
Cannot be updated.
In CamelCase.
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
kind
required string proapiVersion
required string pro
APIVersion defines the versioned schema of this representation of an object.
Servers should convert recognized schemas to the latest internal value, and
may reject unrecognized values.
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
apiVersion
required string prometadata
required object pro
metadata
required object proname
required string pro
Name must be unique within a namespace. Is required when creating resources, although
some resources may allow a client to request the generation of an appropriate name
automatically. Name is primarily intended for creation idempotence and configuration
definition.
Cannot be updated.
More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#names
name
required string progenerateName
required string pro
GenerateName is an optional prefix, used by the server, to generate a unique
name ONLY IF the Name field has not been provided.
If this field is used, the name returned to the client will be different
than the name passed. This value will also be combined with a unique suffix.
The provided value has the same validation rules as the Name field,
and may be truncated by the length of the suffix required to make the value
unique on the server.
If this field is specified and the generated name exists, the server will return a 409.
Applied only if Name is not specified.
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#idempotency
generateName
required string pronamespace
required string pro
Namespace defines the space within which each name must be unique. An empty namespace is
equivalent to the "default" namespace, but "default" is the canonical representation.
Not all objects are required to be scoped to a namespace - the value of this field for
those objects will be empty.
Must be a DNS_LABEL.
Cannot be updated.
More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces
namespace
required string proselfLink
required string pro
Deprecated: selfLink is a legacy read-only field that is no longer populated by the system.
selfLink
required string prouid
required string pro
UID is the unique in time and space value for this object. It is typically generated by
the server on successful creation of a resource and is not allowed to change on PUT
operations.
Populated by the system.
Read-only.
More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids
uid
required string proresourceVersion
required string pro
An opaque value that represents the internal version of this object that can
be used by clients to determine when objects have changed. May be used for optimistic
concurrency, change detection, and the watch operation on a resource or set of resources.
Clients must treat these values as opaque and passed unmodified back to the server.
They may only be valid for a particular resource or set of resources.
Populated by the system.
Read-only.
Value must be treated as opaque by clients and .
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency
resourceVersion
required string progeneration
required integer pro
A sequence number representing a specific generation of the desired state.
Populated by the system. Read-only.
generation
required integer procreationTimestamp
required object pro
CreationTimestamp is a timestamp representing the server time when this object was
created. It is not guaranteed to be set in happens-before order across separate operations.
Clients may not set this value. It is represented in RFC3339 form and is in UTC.
Populated by the system.
Read-only.
Null for lists.
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
creationTimestamp
required object prodeletionTimestamp
required object pro
DeletionTimestamp is RFC 3339 date and time at which this resource will be deleted. This
field is set by the server when a graceful deletion is requested by the user, and is not
directly settable by a client. The resource is expected to be deleted (no longer visible
from resource lists, and not reachable by name) after the time in this field, once the
finalizers list is empty. As long as the finalizers list contains items, deletion is blocked.
Once the deletionTimestamp is set, this value may not be unset or be set further into the
future, although it may be shortened or the resource may be deleted prior to this time.
For example, a user may request that a pod is deleted in 30 seconds. The Kubelet will react
by sending a graceful termination signal to the containers in the pod. After that 30 seconds,
the Kubelet will send a hard termination signal (SIGKILL) to the container and after cleanup,
remove the pod from the API. In the presence of network partitions, this object may still
exist after this timestamp, until an administrator or automated process can determine the
resource is fully terminated.
If not set, graceful deletion of the object has not been requested.
Populated by the system when a graceful deletion is requested.
Read-only.
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
deletionTimestamp
required object prodeletionGracePeriodSeconds
required integer pro
Number of seconds allowed for this object to gracefully terminate before
it will be removed from the system. Only set when deletionTimestamp is also set.
May only be shortened.
Read-only.
deletionGracePeriodSeconds
required integer prolabels
required object pro
Map of string keys and values that can be used to organize and categorize
(scope and select) objects. May match selectors of replication controllers
and services.
More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels
labels
required object proannotations
required object pro
Annotations is an unstructured key value map stored with a resource that may be
set by external tools to store and retrieve arbitrary metadata. They are not
queryable and should be preserved when modifying objects.
More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations
annotations
required object proownerReferences
required object[] pro
List of objects depended by this object. If ALL objects in the list have
been deleted, this object will be garbage collected. If this object is managed by a controller,
then an entry in this list will point to this controller, with the controller field set to true.
There cannot be more than one managing controller.
ownerReferences
required object[] proapiVersion
required string pro
API version of the referent.
apiVersion
required string prokind
required string pro
Kind of the referent.
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
kind
required string proname
required string pro
Name of the referent.
More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#names
name
required string prouid
required string pro
UID of the referent.
More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids
uid
required string procontroller
required boolean pro
If true, this reference points to the managing controller.
controller
required boolean problockOwnerDeletion
required boolean pro
If true, AND if the owner has the "foregroundDeletion" finalizer, then
the owner cannot be deleted from the key-value store until this
reference is removed.
See https://kubernetes.io/docs/concepts/architecture/garbage-collection/#foreground-deletion
for how the garbage collector interacts with this field and enforces the foreground deletion.
Defaults to false.
To set this field, a user needs "delete" permission of the owner,
otherwise 422 (Unprocessable Entity) will be returned.
blockOwnerDeletion
required boolean profinalizers
required string[] pro
Must be empty before the object is deleted from the registry. Each entry
is an identifier for the responsible component that will remove the entry
from the list. If the deletionTimestamp of the object is non-nil, entries
in this list can only be removed.
Finalizers may be processed and removed in any order. Order is NOT enforced
because it introduces significant risk of stuck finalizers.
finalizers is a shared field, any actor with permission can reorder it.
If the finalizer list is processed in order, then this can lead to a situation
in which the component responsible for the first finalizer in the list is
waiting for a signal (field value, external system, or other) produced by a
component responsible for a finalizer later in the list, resulting in a deadlock.
Without enforced ordering finalizers are free to order amongst themselves and
are not vulnerable to ordering changes in the list.
finalizers
required string[] promanagedFields
required object[] pro
ManagedFields maps workflow-id and version to the set of fields
that are managed by that workflow. This is mostly for internal
housekeeping, and users typically shouldn't need to set or
understand this field. A workflow can be the user's name, a
controller's name, or the name of a specific apply path like
"ci-cd". The set of fields is always in the version that the
workflow used when modifying the object.
managedFields
required object[] promanager
required string pro
Manager is an identifier of the workflow managing these fields.
manager
required string prooperation
required string pro
Operation is the type of operation which lead to this ManagedFieldsEntry being created.
The only valid values for this field are 'Apply' and 'Update'.
operation
required string proapiVersion
required string pro
APIVersion defines the version of this resource that this field set
applies to. The format is "group/version" just like the top-level
APIVersion field. It is necessary to track the version of a field
set because it cannot be automatically converted.
apiVersion
required string protime
required object pro
Time is the timestamp of when the ManagedFields entry was added. The
timestamp will also be updated if a field is added, the manager
changes any of the owned fields value or removes a field. The
timestamp does not update when a field is removed from the entry
because another manager took it over.
time
required object profieldsType
required string pro
FieldsType is the discriminator for the different fields format and version.
There is currently only one possible value: "FieldsV1"
fieldsType
required string profieldsV1
required object pro
FieldsV1 holds the first JSON version format as described in the "FieldsV1" type.
fieldsV1
required object prosubresource
required string pro
Subresource is the name of the subresource used to update that object, or
empty string if the object was updated through the main resource. The
value of this field is used to distinguish between managers, even if they
share the same name. For example, a status update will be distinct from a
regular update using the same manager name.
Note that the APIVersion field is not related to the Subresource field and
it always corresponds to the version of the main resource.
subresource
required string prospec
required object pro
spec
required object prodisplayName
required string pro
DisplayName is the name that is shown in the UI
displayName
required string prodescription
required string pro
Description describes the virtual cluster template
description
required string proowner
required object pro
Owner holds the owner of this object
owner
required object protemplate
required object pro
Template holds the virtual cluster template
template
required object prometadata
required object pro
metadata
required object proinstanceTemplate
required object pro
InstanceTemplate holds the virtual cluster instance template
instanceTemplate
required object proapps
required object[] pro
Apps specifies the apps that should get deployed by this template
apps
required object[] proname
required string pro
Name of the target app
name
required string pronamespace
required string pro
Namespace specifies in which target namespace the app should
get deployed in
namespace
required string proreleaseName
required string pro
ReleaseName is the name of the app release
releaseName
required string proversion
required string pro
Version of the app
version
required string proparameters
required string pro
Parameters to use for the app
parameters
required string procharts
required object[] pro
Charts are helm charts that should get deployed
charts
required object[] proname
required string pro
Name is the chart name in the repository
name
required string proversion
required string pro
Version is the chart version in the repository
version
required string prorepoURL
required string pro
RepoURL is the repo url where the chart can be found
repoURL
required string prousername
required string pro
The username that is required for this repository
username
required string prousernameRef
required object pro
The username that is required for this repository
usernameRef
required object propassword
required string pro
The password that is required for this repository
password
required string propasswordRef
required object pro
The password that is required for this repository
passwordRef
required object proinsecureSkipTlsVerify
required boolean pro
If tls certificate checks for the chart download should be skipped
insecureSkipTlsVerify
required boolean proreleaseName
required string pro
ReleaseName is the preferred release name of the app
releaseName
required string proreleaseNamespace
required string pro
ReleaseNamespace is the preferred release namespace of the app
releaseNamespace
required string provalues
required string pro
Values are the values that should get passed to the chart
values
required string prowait
required boolean pro
Wait determines if Loft should wait during deploy for the app to become ready
wait
required boolean protimeout
required string pro
Timeout is the time to wait for any individual Kubernetes operation (like Jobs for hooks) (default 5m0s)
timeout
required string proobjects
required string pro
Objects are Kubernetes style yamls that should get deployed into the virtual cluster
objects
required string proaccess
required object pro
Access defines the access of users and teams to the virtual cluster.
access
required object prodefaultClusterRole
required string pro
Specifies which cluster role should get applied to users or teams that do not
match a rule below.
defaultClusterRole
required string prorules
required object[] pro
Rules defines which users and teams should have which access to the virtual
cluster. If no rule matches an authenticated incoming user, the user will get cluster admin
access.
rules
required object[] propro
required object pro
Pro defines the pro settings for the virtual cluster
pro
required object proenabled
required boolean pro
Enabled defines if the virtual cluster is a pro cluster or not
enabled
required boolean prohelmRelease
required object pro
HelmRelease is the helm release configuration for the virtual cluster.
helmRelease
required object prochart
required object pro
infos about what chart to deploy
chart
required object proname
required string pro
the name of the helm chart
name
required string prorepo
required string pro
the repo of the helm chart
repo
required string prousername
required string pro
The username that is required for this repository
username
required string propassword
required string pro
The password that is required for this repository
password
required string proversion
required string pro
the version of the helm chart to use
version
required string provalues
required string pro
the values for the given chart
values
required string proaccessPoint
required object pro
AccessPoint defines settings to expose the virtual cluster directly via an ingress rather than
through the (default) Loft proxy
accessPoint
required object proingress
required object pro
Ingress defines virtual cluster access via ingress
ingress
required object proenabled
required boolean pro
Enabled defines if the virtual cluster access point (via ingress) is enabled or not; requires
the connected cluster to have the loft.sh/ingress-suffix
annotation set to define the domain
name suffix used for the ingress.
enabled
required boolean proloft.sh/ingress-suffix
annotation set to define the domain
name suffix used for the ingress.forwardToken
required boolean pro
ForwardToken signals the proxy to pass through the used token to the virtual Kubernetes
api server and do a TokenReview there.
forwardToken
required boolean prospaceTemplate
required object pro
SpaceTemplate holds the space template
spaceTemplate
required object prometadata
required object pro
metadata
required object proobjects
required string pro
Objects are Kubernetes style yamls that should get deployed into the virtual cluster namespace
objects
required string procharts
required object[] pro
Charts are helm charts that should get deployed
charts
required object[] proname
required string pro
Name is the chart name in the repository
name
required string proversion
required string pro
Version is the chart version in the repository
version
required string prorepoURL
required string pro
RepoURL is the repo url where the chart can be found
repoURL
required string prousername
required string pro
The username that is required for this repository
username
required string prousernameRef
required object pro
The username that is required for this repository
usernameRef
required object propassword
required string pro
The password that is required for this repository
password
required string propasswordRef
required object pro
The password that is required for this repository
passwordRef
required object proinsecureSkipTlsVerify
required boolean pro
If tls certificate checks for the chart download should be skipped
insecureSkipTlsVerify
required boolean proreleaseName
required string pro
ReleaseName is the preferred release name of the app
releaseName
required string proreleaseNamespace
required string pro
ReleaseNamespace is the preferred release namespace of the app
releaseNamespace
required string provalues
required string pro
Values are the values that should get passed to the chart
values
required string prowait
required boolean pro
Wait determines if Loft should wait during deploy for the app to become ready
wait
required boolean protimeout
required string pro
Timeout is the time to wait for any individual Kubernetes operation (like Jobs for hooks) (default 5m0s)
timeout
required string proapps
required object[] pro
Apps specifies the apps that should get deployed by this template
apps
required object[] proname
required string pro
Name of the target app
name
required string pronamespace
required string pro
Namespace specifies in which target namespace the app should
get deployed in
namespace
required string proreleaseName
required string pro
ReleaseName is the name of the app release
releaseName
required string proversion
required string pro
Version of the app
version
required string proparameters
required string pro
Parameters to use for the app
parameters
required string proparameters
required object[] pro
Parameters define additional app parameters that will set helm values
parameters
required object[] provariable
required string pro
Variable is the path of the variable. Can be foo or foo.bar for nested objects.
variable
required string prolabel
required string pro
Label is the label to show for this parameter
label
required string prodescription
required string pro
Description is the description to show for this parameter
description
required string protype
required string pro
Type of the parameter. Can be one of:
string, multiline, boolean, number and password
type
required string prooptions
required string[] pro
Options is a slice of strings, where each string represents a mutually exclusive choice.
options
required string[] promin
required integer pro
Min is the minimum number if type is number
min
required integer promax
required integer pro
Max is the maximum number if type is number
max
required integer prorequired
required boolean pro
Required specifies if this parameter is required
required
required boolean prodefaultValue
required string pro
DefaultValue is the default value if none is specified
defaultValue
required string proplaceholder
required string pro
Placeholder shown in the UI
placeholder
required string proinvalidation
required string pro
Invalidation regex that if matched will reject the input
invalidation
required string provalidation
required string pro
Validation regex that if matched will allow the input
validation
required string prosection
required string pro
Section where this app should be displayed. Apps with the same section name will be grouped together
section
required string proversions
required object[] pro
Versions are different versions of the template that can be referenced as well
versions
required object[] protemplate
required object pro
Template holds the space template
template
required object prometadata
required object pro
metadata
required object proinstanceTemplate
required object pro
InstanceTemplate holds the virtual cluster instance template
instanceTemplate
required object proapps
required object[] pro
Apps specifies the apps that should get deployed by this template
apps
required object[] proname
required string pro
Name of the target app
name
required string pronamespace
required string pro
Namespace specifies in which target namespace the app should
get deployed in
namespace
required string proreleaseName
required string pro
ReleaseName is the name of the app release
releaseName
required string proversion
required string pro
Version of the app
version
required string proparameters
required string pro
Parameters to use for the app
parameters
required string procharts
required object[] pro
Charts are helm charts that should get deployed
charts
required object[] proname
required string pro
Name is the chart name in the repository
name
required string proversion
required string pro
Version is the chart version in the repository
version
required string prorepoURL
required string pro
RepoURL is the repo url where the chart can be found
repoURL
required string prousername
required string pro
The username that is required for this repository
username
required string prousernameRef
required object pro
The username that is required for this repository
usernameRef
required object propassword
required string pro
The password that is required for this repository
password
required string propasswordRef
required object pro
The password that is required for this repository
passwordRef
required object proinsecureSkipTlsVerify
required boolean pro
If tls certificate checks for the chart download should be skipped
insecureSkipTlsVerify
required boolean proreleaseName
required string pro
ReleaseName is the preferred release name of the app
releaseName
required string proreleaseNamespace
required string pro
ReleaseNamespace is the preferred release namespace of the app
releaseNamespace
required string provalues
required string pro
Values are the values that should get passed to the chart
values
required string prowait
required boolean pro
Wait determines if Loft should wait during deploy for the app to become ready
wait
required boolean protimeout
required string pro
Timeout is the time to wait for any individual Kubernetes operation (like Jobs for hooks) (default 5m0s)
timeout
required string proobjects
required string pro
Objects are Kubernetes style yamls that should get deployed into the virtual cluster
objects
required string proaccess
required object pro
Access defines the access of users and teams to the virtual cluster.
access
required object prodefaultClusterRole
required string pro
Specifies which cluster role should get applied to users or teams that do not
match a rule below.
defaultClusterRole
required string prorules
required object[] pro
Rules defines which users and teams should have which access to the virtual
cluster. If no rule matches an authenticated incoming user, the user will get cluster admin
access.
rules
required object[] propro
required object pro
Pro defines the pro settings for the virtual cluster
pro
required object proenabled
required boolean pro
Enabled defines if the virtual cluster is a pro cluster or not
enabled
required boolean prohelmRelease
required object pro
HelmRelease is the helm release configuration for the virtual cluster.
helmRelease
required object prochart
required object pro
infos about what chart to deploy
chart
required object proname
required string pro
the name of the helm chart
name
required string prorepo
required string pro
the repo of the helm chart
repo
required string prousername
required string pro
The username that is required for this repository
username
required string propassword
required string pro
The password that is required for this repository
password
required string proversion
required string pro
the version of the helm chart to use
version
required string provalues
required string pro
the values for the given chart
values
required string proaccessPoint
required object pro
AccessPoint defines settings to expose the virtual cluster directly via an ingress rather than
through the (default) Loft proxy
accessPoint
required object proingress
required object pro
Ingress defines virtual cluster access via ingress
ingress
required object proenabled
required boolean pro
Enabled defines if the virtual cluster access point (via ingress) is enabled or not; requires
the connected cluster to have the loft.sh/ingress-suffix
annotation set to define the domain
name suffix used for the ingress.
enabled
required boolean proloft.sh/ingress-suffix
annotation set to define the domain
name suffix used for the ingress.forwardToken
required boolean pro
ForwardToken signals the proxy to pass through the used token to the virtual Kubernetes
api server and do a TokenReview there.
forwardToken
required boolean prospaceTemplate
required object pro
SpaceTemplate holds the space template
spaceTemplate
required object prometadata
required object pro
metadata
required object proobjects
required string pro
Objects are Kubernetes style yamls that should get deployed into the virtual cluster namespace
objects
required string procharts
required object[] pro
Charts are helm charts that should get deployed
charts
required object[] proname
required string pro
Name is the chart name in the repository
name
required string proversion
required string pro
Version is the chart version in the repository
version
required string prorepoURL
required string pro
RepoURL is the repo url where the chart can be found
repoURL
required string prousername
required string pro
The username that is required for this repository
username
required string prousernameRef
required object pro
The username that is required for this repository
usernameRef
required object propassword
required string pro
The password that is required for this repository
password
required string propasswordRef
required object pro
The password that is required for this repository
passwordRef
required object proinsecureSkipTlsVerify
required boolean pro
If tls certificate checks for the chart download should be skipped
insecureSkipTlsVerify
required boolean proreleaseName
required string pro
ReleaseName is the preferred release name of the app
releaseName
required string proreleaseNamespace
required string pro
ReleaseNamespace is the preferred release namespace of the app
releaseNamespace
required string provalues
required string pro
Values are the values that should get passed to the chart
values
required string prowait
required boolean pro
Wait determines if Loft should wait during deploy for the app to become ready
wait
required boolean protimeout
required string pro
Timeout is the time to wait for any individual Kubernetes operation (like Jobs for hooks) (default 5m0s)
timeout
required string proapps
required object[] pro
Apps specifies the apps that should get deployed by this template
apps
required object[] proname
required string pro
Name of the target app
name
required string pronamespace
required string pro
Namespace specifies in which target namespace the app should
get deployed in
namespace
required string proreleaseName
required string pro
ReleaseName is the name of the app release
releaseName
required string proversion
required string pro
Version of the app
version
required string proparameters
required string pro
Parameters to use for the app
parameters
required string proparameters
required object[] pro
Parameters define additional app parameters that will set helm values
parameters
required object[] provariable
required string pro
Variable is the path of the variable. Can be foo or foo.bar for nested objects.
variable
required string prolabel
required string pro
Label is the label to show for this parameter
label
required string prodescription
required string pro
Description is the description to show for this parameter
description
required string protype
required string pro
Type of the parameter. Can be one of:
string, multiline, boolean, number and password
type
required string prooptions
required string[] pro
Options is a slice of strings, where each string represents a mutually exclusive choice.
options
required string[] promin
required integer pro
Min is the minimum number if type is number
min
required integer promax
required integer pro
Max is the maximum number if type is number
max
required integer prorequired
required boolean pro
Required specifies if this parameter is required
required
required boolean prodefaultValue
required string pro
DefaultValue is the default value if none is specified
defaultValue
required string proplaceholder
required string pro
Placeholder shown in the UI
placeholder
required string proinvalidation
required string pro
Invalidation regex that if matched will reject the input
invalidation
required string provalidation
required string pro
Validation regex that if matched will allow the input
validation
required string prosection
required string pro
Section where this app should be displayed. Apps with the same section name will be grouped together
section
required string proversion
required string pro
Version is the version. Needs to be in X.X.X format.
version
required string proaccess
required object[] pro
Access holds the access rights for users and teams
access
required object[] proname
required string pro
Name is an optional name that is used for this access rule
name
required string proverbs
required string[] pro
Verbs is a list of Verbs that apply to ALL the ResourceKinds and AttributeRestrictions contained in this rule. VerbAll represents all kinds.
verbs
required string[] prosubresources
required string[] pro
Subresources defines the sub resources that are allowed by this access rule
subresources
required string[] prousers
required string[] pro
Users specifies which users should be able to access this secret with the aforementioned verbs
users
required string[] proteams
required string[] pro
Teams specifies which teams should be able to access this secret with the aforementioned verbs
teams
required string[] prostatus
required object pro
status
required object proRetrieve: Virtual Cluster Templates
You can either use curl or kubectl to retrieve Virtual Cluster Templates.
- kubectl
- curl
Retrieve a list of Virtual Cluster Templates
Run the following command to list all Virtual Cluster Templates:
kubectl get virtualclustertemplates.management.loft.sh -o yaml
Retrieve a single Virtual Cluster Template by name
Run the following kubectl command to get Virtual Cluster Template my-virtual-cluster-template
:
kubectl get virtualclustertemplates.management.loft.sh my-virtual-cluster-template -o yaml
Retrieve a list of Virtual Cluster Templates
Run the following curl command to list all Virtual Cluster Templates:
curl -s "https://$LOFT_DOMAIN/kubernetes/management/apis/management.loft.sh/v1/virtualclustertemplates" \
-X GET --insecure \
-H "Authorization: Bearer $ACCESS_KEY"
Get a single Virtual Cluster Template by name
Run the following curl command to get Virtual Cluster Template my-virtual-cluster-template
:
# Exchange my-virtual-cluster-template in the url below with the name of the Virtual Cluster Template
curl -s "https://$LOFT_DOMAIN/kubernetes/management/apis/management.loft.sh/v1/virtualclustertemplates/my-virtual-cluster-template" \
-X GET --insecure \
-H "Authorization: Bearer $ACCESS_KEY"
Create: Virtual Cluster Template
You can either use curl or kubectl to create a new Virtual Cluster Template.
- kubectl
- curl
Create a file object.yaml
with the following contents:
apiVersion: management.loft.sh/v1
kind: VirtualClusterTemplate
metadata:
creationTimestamp: null
name: my-virtual-cluster-template
spec:
access:
- users:
- '*'
verbs:
- get
description: This virtual cluster template deploys an isolated virtual cluster
displayName: Isolated Virtual Cluster Template
template:
accessPoint:
ingress: {}
helmRelease:
chart: {}
values: |-
# Below you can configure the virtual cluster
isolation:
enabled: true
# Checkout https://vcluster.com/docs for more config options
instanceTemplate:
metadata: {}
metadata: {}
pro: {}
spaceTemplate:
metadata: {}
status: {}
Then create the Virtual Cluster Template my-virtual-cluster-template
with:
kubectl create -f object.yaml
Create a file object.yaml
with the following contents:
apiVersion: management.loft.sh/v1
kind: VirtualClusterTemplate
metadata:
creationTimestamp: null
name: my-virtual-cluster-template
spec:
access:
- users:
- '*'
verbs:
- get
description: This virtual cluster template deploys an isolated virtual cluster
displayName: Isolated Virtual Cluster Template
template:
accessPoint:
ingress: {}
helmRelease:
chart: {}
values: |-
# Below you can configure the virtual cluster
isolation:
enabled: true
# Checkout https://vcluster.com/docs for more config options
instanceTemplate:
metadata: {}
metadata: {}
pro: {}
spaceTemplate:
metadata: {}
status: {}
Run the following curl command to create a new Virtual Cluster Template my-virtual-cluster-template
:
curl -s -X POST --insecure \
"https://$LOFT_DOMAIN/kubernetes/management/apis/management.loft.sh/v1/virtualclustertemplates" \
--data-binary "$(cat object.yaml)" \
-H "Content-Type: application/yaml" \
-H "Authorization: Bearer $ACCESS_KEY"
Update: Virtual Cluster Template
You can either use curl or kubectl to update Virtual Cluster Templates.
- kubectl
- curl
Update Virtual Cluster Template
Run the following command to update Virtual Cluster Template my-virtual-cluster-template
:
kubectl edit virtualclustertemplates.management.loft.sh my-virtual-cluster-template
Then edit the object and upon save, kubectl will update the resource.
Patch Virtual Cluster Template
Patching a resource is useful if you want to generically exchange only a small portion of the object instead of retrieving the whole object first and then modifying it. To learn more about patches in Kubernetes, please take a look at the official docs.
Run the following kubectl command to add a new annotation my-annotation: my-value
to the Virtual Cluster Template my-virtual-cluster-template
via a patch:
kubectl patch virtualclustertemplates.management.loft.sh my-virtual-cluster-template \
--type json \
-p '[{"op": "add", "path": "/metadata/annotations/my-annotation", "value": "my-value"}]'
Update Virtual Cluster Template
First retrieve the current object into a file object.yaml
. This could look like:
apiVersion: management.loft.sh/v1
kind: VirtualClusterTemplate
metadata:
creationTimestamp: "2023-04-03T00:00:00Z"
generation: 12
name: my-virtual-cluster-template
resourceVersion: "66325905"
uid: af5f9f0f-8ab9-4b4b-a595-a95a5921f3c2
spec:
access:
- users:
- '*'
verbs:
- get
description: This virtual cluster template deploys an isolated virtual cluster
displayName: Isolated Virtual Cluster Template
template:
accessPoint:
ingress: {}
helmRelease:
chart: {}
values: |-
# Below you can configure the virtual cluster
isolation:
enabled: true
# Checkout https://vcluster.com/docs for more config options
instanceTemplate:
metadata: {}
metadata: {}
pro: {}
spaceTemplate:
metadata: {}
status: {}
Run the following curl command to update a single Virtual Cluster Template my-virtual-cluster-template
:
# Replace the my-virtual-cluster-template in the url below with the name of the Virtual Cluster Template you want to update
curl -s "https://$LOFT_DOMAIN/kubernetes/management/apis/management.loft.sh/v1/virtualclustertemplates/my-virtual-cluster-template" \
-X PUT --insecure \
-H "Content-Type: application/yaml" \
-H "Authorization: Bearer $ACCESS_KEY" \
--data-binary "$(cat object.yaml)"
Patch Virtual Cluster Template
Patching a resource is useful if you want to generically exchange only a small portion of the object instead of retrieving the whole object first and then modifying it. To learn more about patches in Kubernetes, please take a look at the official docs.
Run the following curl command to add a new annotation my-annotation: my-value
to the Virtual Cluster Template my-virtual-cluster-template
via a patch:
# Replace the my-virtual-cluster-template in the url below with the name of the Virtual Cluster Template you want to update
curl -s "https://$LOFT_DOMAIN/kubernetes/management/apis/management.loft.sh/v1/virtualclustertemplates/my-virtual-cluster-template" \
-X PATCH --insecure \
-H "Content-Type: application/json-patch+json" \
-H "Authorization: Bearer $ACCESS_KEY" \
--data '[{"op": "add", "path": "/metadata/annotations/my-annotation", "value": "my-value"}]'
Delete: Virtual Cluster Template
You can either use curl or kubectl to delete Virtual Cluster Templates.
- kubectl
- curl
Run the following command to delete Virtual Cluster Template my-virtual-cluster-template
:
kubectl delete virtualclustertemplates.management.loft.sh my-virtual-cluster-template
Run the following curl command to delete Virtual Cluster Template my-virtual-cluster-template
:
# Replace the my-virtual-cluster-template in the url below with the name of the Virtual Cluster Template you want to delete
curl -s "https://$LOFT_DOMAIN/kubernetes/management/apis/management.loft.sh/v1/virtualclustertemplates/my-virtual-cluster-template" \
-X DELETE --insecure \
-H "Authorization: Bearer $ACCESS_KEY"