diff --git a/docs/docs-content/getting-started/aws/create-cluster-profile.md b/docs/docs-content/getting-started/aws/create-cluster-profile.md index bd479d0f920..efc3b3d05d3 100644 --- a/docs/docs-content/getting-started/aws/create-cluster-profile.md +++ b/docs/docs-content/getting-started/aws/create-cluster-profile.md @@ -12,7 +12,7 @@ Palette offers profile-based management for Kubernetes, enabling consistency, re across multiple clusters. A cluster profile allows you to customize the cluster infrastructure stack, allowing you to choose the desired Operating System (OS), Kubernetes, Container Network Interfaces (CNI), Container Storage Interfaces (CSI). You can further customize the stack with add-on application layers. For more information about cluster profile -types, refer to [Cluster Profiles](../cluster-profiles.md). +types, refer to [Cluster Profiles](../introduction.md#cluster-profiles). In this tutorial, you create a full profile directly from the Palette dashboard. Then, you add a layer to your cluster profile by using a [community pack](../../integrations/community_packs.md) to deploy a web application. diff --git a/docs/docs-content/getting-started/aws/update-k8s-cluster.md b/docs/docs-content/getting-started/aws/update-k8s-cluster.md index cda86eba65b..8886963f0d6 100644 --- a/docs/docs-content/getting-started/aws/update-k8s-cluster.md +++ b/docs/docs-content/getting-started/aws/update-k8s-cluster.md @@ -11,9 +11,9 @@ tags: ["getting-started", "aws"] Palette provides cluster profiles, which allow you to specify layers for your workloads using packs, Helm charts, Zarf packages, or cluster manifests. Packs serve as blueprints to the provisioning and deployment process, as they contain the versions of the container images that Palette will install for you. Cluster profiles provide consistency across -environments during the cluster creation process, as well as when maintaining your clusters. Check out the -[cluster profiles](../cluster-profiles.md) page to learn more. Once provisioned, there are three main ways to update -your Palette deployments. +environments during the cluster creation process, as well as when maintaining your clusters. Check out +[Cluster Profiles](../introduction.md#cluster-profiles) to learn more. Once provisioned, there are three main ways to +update your Palette deployments. | Method | Description | Cluster application process | | ------------------------ | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/docs/docs-content/getting-started/azure/create-cluster-profile.md b/docs/docs-content/getting-started/azure/create-cluster-profile.md index b678120da45..977fdd0db16 100644 --- a/docs/docs-content/getting-started/azure/create-cluster-profile.md +++ b/docs/docs-content/getting-started/azure/create-cluster-profile.md @@ -12,7 +12,7 @@ Palette offers profile-based management for Kubernetes, enabling consistency, re across multiple clusters. A cluster profile allows you to customize the cluster infrastructure stack, allowing you to choose the desired Operating System (OS), Kubernetes, Container Network Interfaces (CNI), Container Storage Interfaces (CSI). You can further customize the stack with add-on application layers. For more information about cluster profile -types, refer to [Cluster Profiles](../cluster-profiles.md). +types, refer to [Cluster Profiles]((../introduction.md#cluster-profiles). In this tutorial, you create a full profile directly from the Palette dashboard. Then, you add a layer to your cluster profile by using a [community pack](../../integrations/community_packs.md) to deploy a web application. diff --git a/docs/docs-content/getting-started/azure/update-k8s-cluster.md b/docs/docs-content/getting-started/azure/update-k8s-cluster.md index f35cd026907..48fb6d818c5 100644 --- a/docs/docs-content/getting-started/azure/update-k8s-cluster.md +++ b/docs/docs-content/getting-started/azure/update-k8s-cluster.md @@ -11,9 +11,9 @@ tags: ["getting-started", "azure"] Palette provides cluster profiles, which allow you to specify layers for your workloads using packs, Helm charts, Zarf packages, or cluster manifests. Packs serve as blueprints to the provisioning and deployment process, as they contain the versions of the container images that Palette will install for you. Cluster profiles provide consistency across -environments during the cluster creation process, as well as when maintaining your clusters. Check out the -[cluster profiles](../cluster-profiles.md) page to learn more. Once provisioned, there are three main ways to update -your Palette deployments. +environments during the cluster creation process, as well as when maintaining your clusters. Check out +[Cluster Profiles](../introduction.md#cluster-profiles) to learn more. Once provisioned, there are three main ways to +update your Palette deployments. | Method | Description | Cluster application process | | ------------------------ | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/docs/docs-content/getting-started/cluster-profiles.md b/docs/docs-content/getting-started/cluster-profiles.md deleted file mode 100644 index 09c24edfd36..00000000000 --- a/docs/docs-content/getting-started/cluster-profiles.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -sidebar_label: "Cluster Profiles" -title: "Cluster Profiles" -description: "Spectro Cloud Palette Cluster Profiles" -icon: "" -hide_table_of_contents: false -sidebar_position: 30 -tags: ["getting-started"] ---- - -Cluster profiles are the declarative, full-stack models that Palette follows when it provisions, scales, and maintains -your clusters. Cluster profiles are composed of layers using packs, Helm charts, Zarf packages, or cluster manifests to -meet specific types of workloads on your Palette cluster deployments. You can create as many profiles as needed for your -workloads. - -Cluster profiles provide you with a repeatable deployment process for all of your development and production -environments. They also give you visibility on the layers, packages and versions present on your deployed clusters. - -Finally, if you want to update or maintain your deployed workloads, cluster profiles give you the flexibility to make -changes to all clusters deployed with the profile by removing, swapping or adding a new layer. Palette will then -reconcile the current state of your workloads with the desired state specified by the profile. - -Below are cluster profile types you can create: - -- _Infrastructure_ profiles provide the essential components for workload cluster deployments within a - [tenant](../glossary-all.md#tenant): Operating System (OS), Kubernetes, Network, and Storage. Collectively, these - layers form the infrastructure for your cluster. - -- _Add-on_ profiles are exclusively composed of add-on layers. They usually do not contain infrastructure components and - are instead designed for reusability across multiple clusters and multiple projects within a tenant. Since they - provide the flexibility to configure clusters based on specific requirements, _add-on_ profiles can be added to - _infrastructure_ profiles to create what we call a _full profile_. - -- _Full profiles_ combine infrastructure packs with add-on layers. By adding layers, you can enhance cluster - functionality. For example, you might add system apps, authentication, monitoring, ingress, load balancers, and more - to your cluster. - -The diagram below illustrates the components of these profile types and how you can build on infrastructure layers with -add-on layers to create a full cluster profile. You can also create separate add-on profiles to reuse among multiple -clusters. - -![A flow diagram that shows how you can add layers to an infrastructure profile to create a full profile.](/getting-started/getting-started_cluster-profiles_cluster-profiles.webp) - -## Packs - -Packs are the smallest component of a cluster profile. Each layer of a cluster profile is made up of a specific pack. -Palette provides packs that are tailored for specific uses to support the core infrastructure a cluster needs. You can -also use add-on packs, or create your own custom pack to extend Kubernetes functionality. - -The diagram below illustrates some of the popular technologies that you can use in your cluster profile layers. Check -out the [Packs List](../integrations/integrations.mdx) page to learn more about individual packs. - -![Diagram of stack grouped as a unit](/getting-started/getting-started_cluster-profiles_stack-grouped-packs.webp) diff --git a/docs/docs-content/getting-started/gcp/create-cluster-profile.md b/docs/docs-content/getting-started/gcp/create-cluster-profile.md index b21e6204a65..7d13b961c88 100644 --- a/docs/docs-content/getting-started/gcp/create-cluster-profile.md +++ b/docs/docs-content/getting-started/gcp/create-cluster-profile.md @@ -12,7 +12,7 @@ Palette offers profile-based management for Kubernetes, enabling consistency, re across multiple clusters. A cluster profile allows you to customize the cluster infrastructure stack, allowing you to choose the desired Operating System (OS), Kubernetes, Container Network Interfaces (CNI), Container Storage Interfaces (CSI). You can further customize the stack with add-on application layers. For more information about cluster profile -types, refer to [Cluster Profiles](../cluster-profiles.md). +types, refer to [Cluster Profiles](../introduction.md#cluster-profiles). In this tutorial, you create a full profile directly from the Palette dashboard. Then, you add a layer to your cluster profile by using a [community pack](../../integrations/community_packs.md) to deploy a web application. diff --git a/docs/docs-content/getting-started/gcp/update-k8s-cluster.md b/docs/docs-content/getting-started/gcp/update-k8s-cluster.md index 7ba316adc7c..4ae76126baf 100644 --- a/docs/docs-content/getting-started/gcp/update-k8s-cluster.md +++ b/docs/docs-content/getting-started/gcp/update-k8s-cluster.md @@ -11,9 +11,9 @@ tags: ["getting-started", "gcp"] Palette provides cluster profiles, which allow you to specify layers for your workloads using packs, Helm charts, Zarf packages, or cluster manifests. Packs serve as blueprints to the provisioning and deployment process, as they contain the versions of the container images that Palette will install for you. Cluster profiles provide consistency across -environments during the cluster creation process, as well as when maintaining your clusters. Check out the -[cluster profiles](../cluster-profiles.md) page to learn more. Once provisioned, there are three main ways to update -your Palette deployments. +environments during the cluster creation process, as well as when maintaining your clusters. Check out +[Cluster Profiles](../introduction.md#cluster-profiles) to learn more. Once provisioned, there are three main ways to +update your Palette deployments. | Method | Description | Cluster application process | | ------------------------ | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/docs/docs-content/getting-started/introduction.md b/docs/docs-content/getting-started/introduction.md index 00b5d30f9db..4d5ad8d29be 100644 --- a/docs/docs-content/getting-started/introduction.md +++ b/docs/docs-content/getting-started/introduction.md @@ -9,39 +9,15 @@ tags: ["getting-started"] --- Palette is a complete and integrated platform that enables organizations to effectively manage the entire lifecycle of -any combination of new or existing, simple or complex, small or large Kubernetes environments, whether in a data center -or the cloud. +any combination of new or existing Kubernetes environments, whether in a data center or the cloud. With a unique approach to managing multiple clusters, Palette gives IT teams complete control, visibility, and production-scale efficiencies to provide developers with highly curated Kubernetes stacks and tools based on their specific needs, with granular governance and enterprise-grade security. -Palette VerteX edition is also available to meet the stringent requirements of regulated industries such as government -and public sector organizations. Palette VerteX integrates Spectro Cloud’s Federal Information Processing Standards -(FIPS) 140-2 cryptographic modules. To learn more about FIPS-enabled Palette, check out -[Palette VerteX](../vertex/vertex.md). - ![Palette product high level overview eager-load](/getting-started/getting-started_introduction_product-overview.webp) -## What Makes Palette Different? - -Palette provides benefits to developers and platform engineers who maintain Kubernetes environments. - -### Full-Stack Management - -Unlike rigid and prepackaged Kubernetes solutions, Palette allows users to construct flexible stacks from OS, -Kubernetes, container network interfaces (CNI), and container storage interfaces (CSI) to additional add-on application -services. As a result, the entire stack - not just the infrastructure - of Kubernetes is deployed, updated, and managed -as one unit, without split responsibility from virtual machines, base OS, Kubernetes infra, and add-ons. - -### End-to-End Declarative Lifecycle Management - -Palette offers the most comprehensive profile-based management for Kubernetes. It enables teams to drive consistency, -repeatability, and operational efficiency across multiple clusters in multiple environments with comprehensive day 0 - -day 2 management. Check out the [Cluster Profiles](./cluster-profiles.md) page to learn more about how cluster profiles -simplifies cluster deployment and maintenance. - -### Any Environment +## Supported Environments Palette has the richest coverage in supported environments that includes: @@ -50,3 +26,52 @@ Palette has the richest coverage in supported environments that includes: - Data Centers: VMware, Nutanix, and OpenStack - Bare Metal: Canonical MAAS - Edge + +The Getting Started section covers deployment flows for clusters hosted in [AWS](./aws/aws.md), +[Azure](./azure/azure.md), [Google Cloud](./gcp/gcp.md) and [VMware vSphere](./vmware/vmware.md). + +## Cluster Profiles + +Cluster profiles are the declarative, full-stack models that Palette follows when it provisions, scales, and maintains +your clusters. Cluster profiles are composed of layers using packs, Helm charts, Zarf packages, or cluster manifests to +meet specific types of workloads on your Palette cluster deployments. You can create as many profiles as needed for your +workloads. + +Cluster profiles provide you with a repeatable deployment process for all of your development and production +environments. They also give you visibility on the layers, packages and versions present on your deployed clusters. + +Finally, if you want to update or maintain your deployed workloads, cluster profiles give you the flexibility to make +changes to all clusters deployed with the profile by removing, swapping or adding a new layer. Palette will then +reconcile the current state of your workloads with the desired state specified by the profile. + +Below are cluster profile types you can create: + +- _Infrastructure_ profiles provide the essential components for workload cluster deployments within a + [tenant](../glossary-all.md#tenant): Operating System (OS), Kubernetes, Network, and Storage. Collectively, these + layers form the infrastructure for your cluster. + +- _Add-on_ profiles are exclusively composed of add-on layers. They usually do not contain infrastructure components and + are instead designed for reusability across multiple clusters and multiple projects within a tenant. Since they + provide the flexibility to configure clusters based on specific requirements, _add-on_ profiles can be added to + _infrastructure_ profiles to create what we call a _full profile_. + +- _Full profiles_ combine infrastructure packs with add-on layers. By adding layers, you can enhance cluster + functionality. For example, you might add system apps, authentication, monitoring, ingress, load balancers, and more + to your cluster. + +The diagram below illustrates the components of these profile types and how you can build on infrastructure layers with +add-on layers to create a full cluster profile. You can also create separate add-on profiles to reuse among multiple +clusters. + +![A flow diagram that shows how you can add layers to an infrastructure profile to create a full profile.](/getting-started/getting-started_cluster-profiles_cluster-profiles.webp) + +## Packs + +Packs are the smallest component of a cluster profile. Each layer of a cluster profile is made up of a specific pack. +Palette provides packs that are tailored for specific uses to support the core infrastructure a cluster needs. You can +also use add-on packs, or create your own custom pack to extend Kubernetes functionality. + +The diagram below illustrates some of the popular technologies that you can use in your cluster profile layers. Check +out the [Packs List](../integrations/integrations.mdx) page to learn more about individual packs. + +![Diagram of stack grouped as a unit](/getting-started/getting-started_cluster-profiles_stack-grouped-packs.webp) diff --git a/docs/docs-content/getting-started/vmware/create-cluster-profile.md b/docs/docs-content/getting-started/vmware/create-cluster-profile.md index f0a5e2d0f61..75e864bfc0b 100644 --- a/docs/docs-content/getting-started/vmware/create-cluster-profile.md +++ b/docs/docs-content/getting-started/vmware/create-cluster-profile.md @@ -12,7 +12,7 @@ Palette offers profile-based management for Kubernetes, enabling consistency, re across multiple clusters. A cluster profile allows you to customize the cluster infrastructure stack, allowing you to choose the desired Operating System (OS), Kubernetes, Container Network Interfaces (CNI), Container Storage Interfaces (CSI). You can further customize the stack with add-on application layers. For more information about cluster profile -types, refer to [Cluster Profiles](../cluster-profiles.md). +types, refer to [Cluster Profiles](../introduction.md#cluster-profiles). In this tutorial, you create a full profile directly from the Palette dashboard. Then, you add a layer to your cluster profile by using a [community pack](../../integrations/community_packs.md) to deploy a web application. diff --git a/docs/docs-content/getting-started/vmware/update-k8s-cluster.md b/docs/docs-content/getting-started/vmware/update-k8s-cluster.md index b28337a51fa..a3c3fbf9de0 100644 --- a/docs/docs-content/getting-started/vmware/update-k8s-cluster.md +++ b/docs/docs-content/getting-started/vmware/update-k8s-cluster.md @@ -11,9 +11,9 @@ tags: ["getting-started", "gcp"] Palette provides cluster profiles, which allow you to specify layers for your workloads using packs, Helm charts, Zarf packages, or cluster manifests. Packs serve as blueprints to the provisioning and deployment process, as they contain the versions of the container images that Palette will install for you. Cluster profiles provide consistency across -environments during the cluster creation process, as well as when maintaining your clusters. Check out the -[cluster profiles](../cluster-profiles.md) page to learn more. Once provisioned, there are three main ways to update -your Palette deployments. +environments during the cluster creation process, as well as when maintaining your clusters. Check out +[Cluster Profiles](../introduction.md#cluster-profiles) to learn more. Once provisioned, there are three main ways to +update your Palette deployments. | Method | Description | Cluster application process | | ------------------------ | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/redirects.js b/redirects.js index fbb3c2058c9..6c59f6b5f14 100644 --- a/redirects.js +++ b/redirects.js @@ -79,6 +79,10 @@ const redirects = [ from: `/getting-started/dashboard`, to: `/introduction/dashboard`, }, + { + from: `/getting-started/cluster-profiles`, + to: `/getting-started/introduction`, + }, { from: `/clusters/public-cloud/eks`, to: `/clusters/public-cloud/aws/eks`, diff --git a/static/assets/docs/images/getting-started/getting-started_introduction_product-overview.webp b/static/assets/docs/images/getting-started/getting-started_introduction_product-overview.webp index f4bdc2ded87..33322eb551f 100644 Binary files a/static/assets/docs/images/getting-started/getting-started_introduction_product-overview.webp and b/static/assets/docs/images/getting-started/getting-started_introduction_product-overview.webp differ