Skip to main content
Version: latest

Bring your own OS (BYOOS)

Versions Supported

Reference Custom Image

Different infrastructure providers have different ways of referencing custom images. The following table provides examples of how to reference custom images for different infrastructure providers.

ProviderExample Image IDosImageOverride ValueNotes
AWSami-0f4804aff4cf9c5a2ami-0f4804aff4cf9c5a2Ensure the AMI is available in the same region as the workload cluster.
Azurehttps://docs.blob.core.windows.net/vhds/ubuntu20-1243.vhdhttps://docs.blob.core.windows.net/vhds/ubuntu20-1243.vhdYou must reference the Azure blob URL of a Virtual Hard Disk (VHD). Image Gallery ID reference is not supported.
Vmware vSpherer_u-2004-0-k-1243-0-new.ovapath/to/template/r_u-2004-0-k-1243-0-new.ovaPoint to the path to where the custom template is located. Palette and VerteX expect OVAs to have the r_u- prefix.
Vmware vSphererhel-8-kube-v1.27.11path/to/template/rhel-8-kube-v1.27.11Point to the path to where the custom template is located.

Image creation tools are available to help you create custom OS images for the infrastructure provider you are using. The following is a list of commonly used tools for creating a custom OS:

Terraform

You can retrieve details about the BYOOS pack by using the following Terraform code.

data "spectrocloud_registry" "public_registry" {
name = "Public Repo"
}

data "spectrocloud_pack_simple" "byoos" {
name = "generic-byoi"
version = "1.0.0"
type = "helm"
registry_uid = data.spectrocloud_registry.public_registry.id
}