diff --git a/_partials/getting-started/_cluster_observability.mdx b/_partials/getting-started/_cluster_observability.mdx index e7b9a211c8..50d056d00c 100644 --- a/_partials/getting-started/_cluster_observability.mdx +++ b/_partials/getting-started/_cluster_observability.mdx @@ -3,7 +3,7 @@ partial_category: getting-started partial_name: cluster-observability --- -As we have seen throughout this tutorial, Palette exposes a set of workload metrics out-of-the-box to help cluster +As we have seen throughout this tutorial, Palette exposes a set of workload metrics out of the box to help cluster administrators better understand the resource utilization of the cluster. The in Palette are a snapshot in time and do not provide alerting capabilities. diff --git a/_partials/getting-started/_getting-started_create-cluster-profile_spacetastic-end.mdx b/_partials/getting-started/_getting-started_create-cluster-profile_spacetastic-end.mdx index c17ee7ba30..d15742ccf5 100644 --- a/_partials/getting-started/_getting-started_create-cluster-profile_spacetastic-end.mdx +++ b/_partials/getting-started/_getting-started_create-cluster-profile_spacetastic-end.mdx @@ -6,7 +6,7 @@ partial_name: spacetastic-create-cluster-profile-end Wren and Kai have created their first Palette cluster profile by following the steps described in this guide. They are in good spirits, as the process has gone smoothly. -> "The visual representation of cluster profiles in Palette is much clearer than our whiteboard." says Kai, glancing +> "The visual representation of cluster profiles in Palette is much clearer than our whiteboard," says Kai, glancing > back at the list they have created. "I can keep track of which versions we are using in production just by reviewing > the profile. What are your thoughts, Wren? Have you remained a Palette skeptic?" > diff --git a/_partials/getting-started/_getting-started_create-cluster-profile_spacetastic-intro.mdx b/_partials/getting-started/_getting-started_create-cluster-profile_spacetastic-intro.mdx index ef45a717c6..8be4d88b4a 100644 --- a/_partials/getting-started/_getting-started_create-cluster-profile_spacetastic-intro.mdx +++ b/_partials/getting-started/_getting-started_create-cluster-profile_spacetastic-intro.mdx @@ -10,7 +10,7 @@ begin to map out all the dependencies of their systems and infrastructure. > making a lot of design decisions myself, as I was Spacetastic's Founding Engineer. It's really interesting to look > back on how much we've built and grown since those days!" > -> Kai smiles and nods. "It's definitely been an out of this world ride!" they say. "I have a similar feeling when I +> Kai smiles and nods. "It's definitely been an out-of-this-world ride!" they say. "I have a similar feeling when I > think about the infrastructure that I built in the early days as Platform Engineer. I will add our infrastructure > layers to your list. This process has the added bonus of giving us a chance to review which dependencies need to be > updated, so Meera, our security expert, will be happy too." diff --git a/_partials/getting-started/_getting-started_deploy-cluster-tf_spacetastic-end.mdx b/_partials/getting-started/_getting-started_deploy-cluster-tf_spacetastic-end.mdx index ebe4ebd208..5e309be1e5 100644 --- a/_partials/getting-started/_getting-started_deploy-cluster-tf_spacetastic-end.mdx +++ b/_partials/getting-started/_getting-started_deploy-cluster-tf_spacetastic-end.mdx @@ -4,11 +4,11 @@ partial_name: spacetastic-deploy-cluster-tf-end --- Wren and Kai have followed this tutorial and have learned how Palette supports IaC through Terraform. They found the -essentials covered to be a great introduction to IaC and gives them the confidence to kick off this initiative at +essentials covered to be a great introduction to IaC, and it gives them the confidence to kick off this initiative at Spacetastic. -> "I'd say that deploying Palette clusters with Terraform is even more convenient than through the UI." says Kai. "The +> "I'd say that deploying Palette clusters with Terraform is even more convenient than through the UI," says Kai. "The > Palette Terraform provider includes a lot of the same functionality that the UI provides." > -> "Yes! I definitely agree. I'm a Terraform novice and I could follow along with this tutorial." says Wren. "This has +> "Yes! I definitely agree. I'm a Terraform novice and I could follow along with this tutorial," says Wren. "This has > definitely inspired me to make our IaC adoption a priority in the medium term future." diff --git a/_partials/getting-started/_getting-started_deploy-cluster-tf_spacetastic-intro.mdx b/_partials/getting-started/_getting-started_deploy-cluster-tf_spacetastic-intro.mdx index 0bb001ce83..7f7ea7f37a 100644 --- a/_partials/getting-started/_getting-started_deploy-cluster-tf_spacetastic-intro.mdx +++ b/_partials/getting-started/_getting-started_deploy-cluster-tf_spacetastic-intro.mdx @@ -4,15 +4,15 @@ partial_name: spacetastic-deploy-cluster-tf-intro --- After following the tutorials in the Getting Started section, the Spacetastic team have been have been impressed with -its capabilities. Wren, Founding Engineer, and Kai, Platform Engineer, have been discussing adopting IaC workflows and +Palette's capabilities. Wren, Founding Engineer, and Kai, Platform Engineer, have been discussing adopting IaC workflows and have been upskilling with Terraform throughout the past year. They are interested in learning if Palette can support IaC workflows too. > "While we're on the topic of platform improvements, it would be great to kick off our adoption of Infrastructure as -> Code at Spacetastic." says Wren. "I've been wanting to roll this out for a while, but we don't have that much in-house +> Code at Spacetastic," says Wren. "I've been wanting to roll this out for a while, but we don't have that much in-house > expertise." > -> "Yes, this would definitely be a big improvement to our processes." says Kai, Platform Engineer. "Some people might +> "Yes, this would definitely be a big improvement to our processes," says Kai, Platform Engineer. "Some people might > think that it slows down the development and release processes, due to the extra code reviews. However, the ability to > revert in the case of an outage more than makes up for this small drop in velocity." > diff --git a/_partials/getting-started/_getting-started_deploy-cluster_spacetastic-end.mdx b/_partials/getting-started/_getting-started_deploy-cluster_spacetastic-end.mdx index eaa1c44596..33659b4a1b 100644 --- a/_partials/getting-started/_getting-started_deploy-cluster_spacetastic-end.mdx +++ b/_partials/getting-started/_getting-started_deploy-cluster_spacetastic-end.mdx @@ -6,17 +6,17 @@ partial_name: spacetastic-deploy-cluster-end Wren and Kai have deployed their first cluster profile by following the steps described in this tutorial. They were impressed by how streamlined the process was and how the cluster profiles provided them with a deployment blueprint. -> "Deploying our first cluster with Palette was intuitive." says Wren. "It's ideal to find an external partner that can +> "Deploying our first cluster with Palette was intuitive," says Wren. "It's ideal to find an external partner that can > take care of our Kubernetes infrastructure and free us up to deliver more educational features. I definitely think > that Palette has the capabilities to take care of all the Kubernetes heavy lifting for us." > -> "I agree with you and I'm glad to hear you're not as skeptical anymore." says Kai, nodding and laughing. "From a +> "I agree with you, and I'm glad to hear you're not as skeptical anymore," says Kai, nodding and laughing. "From a > platform engineering perspective, I can say that cluster profiles will provide us with reliable deployments across > environments and even clouds, so I'm much more confident about our testing and deployment strategy." > -> Meera, Head of Cybersecurity, walks in holding a file. "I've done our security due diligence and I'm happy to report +> Meera, Head of Cybersecurity, walks in holding a file. "I've done our security due diligence, and I'm happy to report > that Spectro Cloud adheres to the highest security standards. I'm happy to approve Palette for use in our > organization." > > "It seems like we've found a great platform that can support us. Let's explore the rest of the Getting Started section -> to understand what else Palette has to offer." says Kai turning back to their monitor. +> to understand what else Palette has to offer," says Kai, turning back to their monitor. diff --git a/_partials/getting-started/_getting-started_deploy-cluster_spacetastic-intro.mdx b/_partials/getting-started/_getting-started_deploy-cluster_spacetastic-intro.mdx index 9792b01100..f47c056334 100644 --- a/_partials/getting-started/_getting-started_deploy-cluster_spacetastic-intro.mdx +++ b/_partials/getting-started/_getting-started_deploy-cluster_spacetastic-intro.mdx @@ -4,12 +4,12 @@ partial_name: spacetastic-deploy-cluster-intro --- After successfully creating their first cluster profile and mapping out their entire technology stack, Wren, Founding -Engineer and Kai, Platform Engineer, continue their Palette onboarding process. They are evaluating Palette as a -potential platform orchestration tool for all the production workloads at Spacetastic, who provide an astronomy +Engineer, and Kai, Platform Engineer, continue their Palette onboarding process. They are evaluating Palette as a +potential platform orchestration tool for all the production workloads at Spacetastic, which provides an astronomy education platform deployed on Kubernetes. > "The Getting Started section is a great way to learn about Palette. The hands-on approach is just what we need to get -> our first cluster deployed." says Kai, scrolling through the Spectro Cloud Docs. "Wren, do you have time to continue +> our first cluster deployed," says Kai, scrolling through the Spectro Cloud Docs. "Wren, do you have time to continue > our onboarding and get our first cluster deployed?" > > Wren sits down next to Kai and sips on a cup of coffee. "Now, we'll get a hands-on feel of the Palette developer diff --git a/_partials/getting-started/_getting-started_landing-page_spacetastic-intro.mdx b/_partials/getting-started/_getting-started_landing-page_spacetastic-intro.mdx index d8f04786e5..d1de5f9ddc 100644 --- a/_partials/getting-started/_getting-started_landing-page_spacetastic-intro.mdx +++ b/_partials/getting-started/_getting-started_landing-page_spacetastic-intro.mdx @@ -4,7 +4,7 @@ partial_name: spacetastic-landing-intro --- Spacetastic Ltd., our fictional example company, is on a mission to teach its users about space. They have assembled a -team of bright minds who are passionate about astronomy and the universe. They are a startup that is gaining popularity, +team of bright minds who are passionate about astronomy and the universe. They are a startup that is gaining popularity as they expand their dashboards and grow their subscribers. Their small team has been in charge of developing new features alongside scaling and maintaining their infrastructure, but they are dedicated to providing the best astronomy education platform on Planet Earth. @@ -12,11 +12,11 @@ education platform on Planet Earth. > "I'm the resident space expert around here!" says Anya, Lead Astrophycist, with a beaming smile. "My mission is to > make astrophysics, the science of space, accessible to everyone." > -> "I'm here to support you and your mission. I build all the dashboards, pages and features that bring your vast space +> "I'm here to support you and your mission. I build all the dashboards, pages, and features that bring your vast space > knowledge to our users in a beautiful visual format!" says Wren, Founding Engineer. > > Kai smiles and nods. "I work closely with both Wren and Anya. As Platform Engineer, I ensure that our platform is -> reliable and scalable for everyone around the world, and beyond!" +> reliable and scalable for everyone around the world and beyond!" > > Meera, Head of Cybersecurity, is the final member of the Spacetastic team. "Let's not forget about the security of our > platform. I make sure that our systems are designed and implemented with security in mind, the true SecDevOps way." @@ -29,7 +29,7 @@ reliability SLA of at least 99% uptime. The following diagram presents an overvi ![Spacetastic system diagram](/getting-started/getting-started_landing_spacetastic-systems.webp) -While the system architecture they have chosen was a great place to start, the team soon face common challenges that +While the system architecture they have chosen was a great place to start, the team soon faced common challenges that many growing organizations encounter with Kubernetes. > Wren hurriedly walks into the office, looking at their phone with a worried expression. "Users are reporting on social @@ -39,6 +39,6 @@ many growing organizations encounter with Kubernetes. > our services without further downtime, as soon as you are able to stabilize our platform." > > "Team, we need to rethink our platform engineering tools. We need a solution that can help us scale and deploy with -> confidence, ultimately supporting the growth of our company." says Kai with a determined look. +> confidence, ultimately supporting the growth of our company," says Kai with a determined look. ![Kubernetes challenges](/getting-started/getting-started_landing_kubernetes-challenges.webp) diff --git a/_partials/getting-started/_getting-started_scale-secure-cluster_spacetastic-end.mdx b/_partials/getting-started/_getting-started_scale-secure-cluster_spacetastic-end.mdx index 7c3ca2973a..5b190079fa 100644 --- a/_partials/getting-started/_getting-started_scale-secure-cluster_spacetastic-end.mdx +++ b/_partials/getting-started/_getting-started_scale-secure-cluster_spacetastic-end.mdx @@ -8,16 +8,16 @@ After going through the steps in the tutorial, Kai is confident in Palette's upg > "What have you found out, Kai?" says Meera walking over to Kai's desk. "Can I rely on Palette when a zero-day > vulnerability comes in?" > -> "Yes, I know how stressful it is when those are reported." says Kai with a sympathetic nod. "I found out that Palette +> "Yes, I know how stressful it is when those are reported," says Kai with a sympathetic nod. "I found out that Palette > has our security covered through their pack updates and scanning capabilities. Relying on this kind of tooling is -> invaluable to security conscious engineers like us." +> invaluable to security-conscious engineers like us." > -> "Excellent! These capabilities will be a great addition to our existing systems at Spacetastic." says Meera with a big +> "Excellent! These capabilities will be a great addition to our existing systems at Spacetastic," says Meera with a big > grin. > > "I'm so glad that we found a platform that can support everyone!" says Kai. "There is so much more to explore though. > I will keep reading through the Getting Started section and find out what additional capabilities Palette provides." > -> "Good thinking, Kai." says Meera, nodding. "We should maximize all of Palette's features now that we have implemented +> "Good thinking, Kai," says Meera, nodding. "We should maximize all of Palette's features now that we have implemented > it in production. We've got big ideas and goals on our company roadmap, so let's find out how Palette can help us > deliver them." diff --git a/_partials/getting-started/_getting-started_scale-secure-cluster_spacetastic-intro.mdx b/_partials/getting-started/_getting-started_scale-secure-cluster_spacetastic-intro.mdx index e9857ffba3..59c6ba611f 100644 --- a/_partials/getting-started/_getting-started_scale-secure-cluster_spacetastic-intro.mdx +++ b/_partials/getting-started/_getting-started_scale-secure-cluster_spacetastic-intro.mdx @@ -9,13 +9,13 @@ platform matures. They must ensure that their systems are patched, upgraded, sca These maintenance tasks must be automated and applied on a schedule, as the entire team wants to focus on providing Spacetastic features. -> "I've read your report on Palette adoption at Spacetastic." says Meera, who provides the security expertise at -> Spacetastic. I was impressed with the ability to roll out updates to all clusters using the same cluster profile. This +> "I've read your report on Palette adoption at Spacetastic," says Meera, who provides the security expertise at +> Spacetastic. "I was impressed with the ability to roll out updates to all clusters using the same cluster profile. This > will streamline our system upgrades and cluster patching. Keeping up with security best practices has never been more > important, now that we are growing faster than ever!" > -> "I agree. No matter how safe our coding practices are, we need to periodically review, patch and upgrade our -> dependencies." says Wren, who leads the engineering team at Spacetastic. +> "I agree. No matter how safe our coding practices are, we need to periodically review, patch, and upgrade our +> dependencies," says Wren, who leads the engineering team at Spacetastic. > > Kai nods, scrolling through the Palette Docs. "Team, Palette has more security and Day-2 operation support than we > have explored so far. I will continue their Getting Started section and report back with my findings." \ No newline at end of file diff --git a/_partials/getting-started/_getting-started_setup_spacetastic-end.mdx b/_partials/getting-started/_getting-started_setup_spacetastic-end.mdx index 8e181053d6..e08f1c3c16 100644 --- a/_partials/getting-started/_getting-started_setup_spacetastic-end.mdx +++ b/_partials/getting-started/_getting-started_setup_spacetastic-end.mdx @@ -6,7 +6,7 @@ partial_name: spacetastic-setup-end After following the detailed Palette setup instructions, the Spacetastic team have added their cloud accounts on the Palette dashboard. They are ready to learn about Palette. -> "The Spectro Cloud team has provided our Palette accounts" says Kai. "I have followed their setup guide and have added +> "The Spectro Cloud team has provided our Palette accounts," says Kai. "I have followed their setup guide and have added > our cloud accounts. I can already tell at a first glance that they offer many Kubernetes customization features." > > Wren joins Kai in looking at the Palette dashboard. "I'm interested to learn more, but I never believe in _magic_ diff --git a/_partials/getting-started/_getting-started_update-cluster_spacetastic-end.mdx b/_partials/getting-started/_getting-started_update-cluster_spacetastic-end.mdx index fc57bcb5f0..a1bbd23cc9 100644 --- a/_partials/getting-started/_getting-started_update-cluster_spacetastic-end.mdx +++ b/_partials/getting-started/_getting-started_update-cluster_spacetastic-end.mdx @@ -6,8 +6,8 @@ partial_name: spacetastic-update-cluster-end Wren and Kai have followed this tutorial and now have a great understanding of what cluster profile updates mean to deployed clusters. They are impressed with Palette's cluster management capabilities. -> "Neat! Palette's cluster profiles allow us to review all updates we apply to our clusters." says Kai. "I can finally +> "Neat! Palette's cluster profiles allow us to review all updates we apply to our clusters," says Kai. "I can finally > take my vacation days, once we can safely maintain our clusters." > -> "Don't I know the feeling?" laughs Wren. "I think we could all use more vacations, quiet weekends and less excitement +> "Don't I know the feeling?" laughs Wren. "I think we could all use more vacations, quiet weekends, and less excitement > when it comes to the Spacetastic platform." diff --git a/_partials/getting-started/_getting-started_update-cluster_spacetastic-intro.mdx b/_partials/getting-started/_getting-started_update-cluster_spacetastic-intro.mdx index 9531a8216f..68eab7bbec 100644 --- a/_partials/getting-started/_getting-started_update-cluster_spacetastic-intro.mdx +++ b/_partials/getting-started/_getting-started_update-cluster_spacetastic-intro.mdx @@ -12,7 +12,7 @@ of the Spacetastic platform and infrastructure. The team have identified the fol > Wren, Founding Engineer, and Kai, Platform Engineer, have been learning and experimenting with Palette. > -> "The streamlined deployment process is just one part of the improvements we've got planned for our platform." says +> "The streamlined deployment process is just one part of the improvements we've got planned for our platform," says > Kai. "I'm interested to learn how Palette's cluster profiles behave when applying updates and other changes to our > clusters." > 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 157352ac4f..91880d9e30 100644 --- a/docs/docs-content/getting-started/aws/create-cluster-profile.md +++ b/docs/docs-content/getting-started/aws/create-cluster-profile.md @@ -10,9 +10,9 @@ tags: ["getting-started", "aws"] Palette offers profile-based management for Kubernetes, enabling consistency, repeatability, and operational efficiency 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](../introduction.md#cluster-profiles). +choose the desired Operating System (OS), Kubernetes, Container Network Interfaces (CNIs), and Container Storage +Interfaces (CSIs). You can further customize the stack with add-on application layers. For more information about +cluster profile 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. The concepts you @@ -104,8 +104,6 @@ preset. Replace these values with your own base64 encoded values. The [_hello-universe_](https://github.com/spectrocloud/hello-universe?tab=readme-ov-file#single-load-balancer) repository provides an unencoded token that you can use. -Click on **Confirm Updates**. The manifest editor closes. - Click on **Confirm & Create** to save the manifest. Then, click on **Save Changes** to save this new layer to the cluster profile. diff --git a/docs/docs-content/getting-started/aws/deploy-k8s-cluster.md b/docs/docs-content/getting-started/aws/deploy-k8s-cluster.md index 43384186f6..7b8eea95ae 100644 --- a/docs/docs-content/getting-started/aws/deploy-k8s-cluster.md +++ b/docs/docs-content/getting-started/aws/deploy-k8s-cluster.md @@ -38,7 +38,8 @@ To complete this tutorial, you will need the following. The following steps will guide you through deploying the cluster infrastructure. -Navigate to the left **Main Menu** and select **Clusters**. Click on **Create Cluster**. +Navigate to the left **Main Menu** and select **Clusters**. Click on **Create Cluster**. If there are existing clusters, +choose **Add New Cluster**. ![Palette clusters overview page](/getting-started/getting-started_deploy-k8s-cluster_new_cluster.webp) @@ -106,9 +107,9 @@ Navigate to the left **Main Menu** and select **Clusters**. ![Update the cluster](/getting-started/aws/getting-started_deploy-k8s-cluster_create_cluster.webp) -The cluster deployment process can take 15 to 30 min. The deployment time varies depending on the cloud provider, -cluster profile, cluster size, and the node pool configurations provided. You can learn more about the deployment -progress by reviewing the event log. Click on the **Events** tab to view the log. +The cluster deployment process can take 15 to 30 minutes. Deployment time varies depending on the cloud provider, +cluster profile, cluster size, and node pool configurations provided. You can learn more about the deployment progress +by reviewing the event log. Choose your cluster and select the **Events** tab to view the log. ![Update the cluster](/getting-started/aws/getting-started_deploy-k8s-cluster_event_log.webp) diff --git a/docs/docs-content/getting-started/aws/scale-secure-cluster.md b/docs/docs-content/getting-started/aws/scale-secure-cluster.md index 8d1715559d..0f5bfa7d1a 100644 --- a/docs/docs-content/getting-started/aws/scale-secure-cluster.md +++ b/docs/docs-content/getting-started/aws/scale-secure-cluster.md @@ -10,8 +10,8 @@ tags: ["getting-started", "aws", "tutorial"] Palette has in-built features to help with the automation of Day-2 operations. Upgrading and maintaining a deployed cluster is typically complex because you need to consider any possible impact on service availability. Palette provides -out-of-the-box functionality for upgrades, observability, granular Role Based Access Control (RBAC), backup and security -scans. +out-of-the-box functionality for upgrades, observability, granular Role Based Access Control (RBAC), backup, and +security scans. This tutorial will teach you how to use the Palette UI to perform scale and maintenance tasks on your clusters. You will learn how to create Palette projects and teams, import a cluster profile, safely upgrade the Kubernetes version of a @@ -33,9 +33,9 @@ Additionally, you should install kubectl locally. Use the Kubernetes ## Create Palette Projects Palette projects help you organize and manage cluster resources, providing logical groupings. They also allow you to -manage user access control through Role Based Access Control (RBAC). You can assign users and teams with specific roles -to specific projects. All resources created within a project are scoped to that project and only available to that -project, but a tenant can have multiple projects. +manage user access control through RBAC. You can assign users and teams with specific roles to specific projects. All +resources created within a project are scoped to that project and only available to that project, but a tenant can have +multiple projects. Log in to [Palette](https://console.spectrocloud.com). @@ -407,18 +407,18 @@ Switch back to Palette in your web browser. Navigate to the left **Main Menu** a cluster profile deployed to your cluster, named `aws-profile`. Ensure that the **1.1.0** version is selected. Click on the **hellouniverse 1.2.0** layer. The manifest editor appears. Set the -`manifests.hello-universe.ui.useTolerations` field on line 20 to `true`. Then, set the -`manifests.hello-universe.ui.effect` field on line 22 to `NoExecute`. This toleration describes that the UI pods of -Hello Universe will tolerate the taint with the key `app`, value `ui` and effect `NoExecute`. The tolerations of the UI +`manifests.hello-universe.ui.useTolerations` field on line 19 to `true`. Then, set the +`manifests.hello-universe.ui.effect` field on line 21 to `NoExecute`. This toleration describes that the UI pods of +Hello Universe will tolerate the taint with the effect `NoExecute`, key `app`, and value `ui`. The tolerations of the UI pods should be as below. ```yaml ui: useTolerations: true tolerations: - effect: NoExecute - key: app - value: ui + effect: NoExecute + key: app + value: ui ``` Click on **Confirm Updates**. The manifest editor closes. Then, click on **Save Changes** to persist your changes. 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 2368860d3f..71fd1f63ad 100644 --- a/docs/docs-content/getting-started/aws/update-k8s-cluster.md +++ b/docs/docs-content/getting-started/aws/update-k8s-cluster.md @@ -64,17 +64,12 @@ panel. ![Image that shows how to add a cluster tag](/getting-started/aws/getting-started_update-k8s-cluster_add-service-tag.webp) -Navigate to the left **Main Menu** and select **Clusters** to view your deployed clusters. Click on **Add Filter**, then -select the **Add custom filter** option. - -Use the drop-down boxes to fill in the values of the filter. Select **Tags** in the left-hand **drop-down Menu**. Select -**is** in the middle **drop-down Menu**. Fill in **service:hello-universe-frontend** in the right-hand input box. - -Click on **Apply Filter**. +Navigate to the left **Main Menu** and select **Clusters** to view your deployed clusters. Click the **filter** icon to +expand the **All Filters** pane, and below **Tags**, enter **service:hello-universe-frontend**. ![Image that shows how to add a frontend service filter](/getting-started/aws/getting-started_update-k8s-cluster_apply-frontend-filter.webp) -Once you apply the filter, only the `aws-cluster` with this tag is displayed. +Only the `aws-cluster` with this tag is displayed. ## Version Cluster Profiles @@ -117,8 +112,7 @@ Click on **Confirm & Create**. The manifest editor closes. Click on **Save Changes** to finish the configuration of this cluster profile version. -Navigate to the left **Main Menu** and select **Clusters**. Filter for the cluster with the -**service:hello-universe-frontend** tag. Select it to view its **Overview** tab. +Navigate to the left **Main Menu** and select **Clusters**. Select the `aws-cluster` to view its **Overview** tab. Select the **Profile** tab of this cluster. You can select a new version of your cluster profile by using the version dropdown. @@ -138,7 +132,7 @@ backups before you make any cluster profile version changes in your production e ::: Palette now makes the required changes to your cluster according to the specifications of the configured cluster profile -version. Once your changes have completed, Palette marks your layers with the green status indicator. The Kubecost pack +version. Once your changes are applied, Palette marks your layers with the green status indicator. The Kubecost pack will be successfully deployed. ![Image that shows completed cluster profile updates](/getting-started/aws/getting-started_update-k8s-cluster_completed-cluster-updates.webp) @@ -181,17 +175,16 @@ the time to recovery in the event of an incident. The process to roll back to a previous version is identical to the process for applying a new version. -Navigate to the left **Main Menu** and select **Clusters**. Filter for the cluster with the -**service:hello-universe-frontend** tag. Select it to view its **Overview** tab. +Navigate to the left **Main Menu** and select **Clusters**. Select the `aws-cluster` to view its **Overview** tab. Select the **Profile** tab. This cluster is currently deployed using cluster profile version **1.1.0**. Select the -option **1.0.0** in the version dropdown. This process is the reverse of what you have done in the previous section, +option **1.0.0** in the version dropdown. This process is the reverse of what you did in the previous section, [Version Cluster Profiles](#version-cluster-profiles). Click on **Save** to confirm your changes. Palette now makes the changes required for the cluster to return to the state specified in version **1.0.0** of your -cluster profile. Once your changes have completed, Palette marks your layers with the green status indicator. +cluster profile. Once your changes are applied, Palette marks your layers with the green status indicator. ![Cluster details page with service URL highlighted](/getting-started/aws/getting-started_deploy-k8s-cluster_service_url.webp) @@ -203,11 +196,10 @@ choose to apply your changes at a convenient time. The previous state of the cluster profile will not be saved once it is overwritten. -Navigate to the left **Main Menu** and select **Clusters**. Filter for the cluster with the tag -**service:hello-universe-frontend**. Select it to view its **Overview** tab. +Navigate to the left **Main Menu** and select **Clusters**. Select the `aws-cluster` to view its **Overview** tab. -Select the **Profile** tab. Then, select the **hello-universe** pack. Change the `replicas` field to `2` on line `15`. -Click on **Save**. The editor closes. +Select the **Profile** tab. Then, select the **hello-universe** pack. Change the `replicas` field on line `15` to `2` +and **Save** your changes. The editor is closed. This cluster now contains an override over its cluster profile. Palette uses the configuration you have just provided for the single cluster over its cluster profile and begins making the appropriate changes. @@ -215,20 +207,20 @@ for the single cluster over its cluster profile and begins making the appropriat Once these changes are complete, select the **Workloads** tab. Then, select the **hello-universe** namespace. Two **ui** pods are available, instead of the one specified by your cluster profile. Your override has been successfully -applied. +applied. If your changes are not displayed, use the **refresh** icon. Navigate to the left **Main Menu** and select **Profiles** to view the cluster profile page. Find the cluster profile corresponding to your _hello-universe-frontend_ cluster. It is named `aws-profile`. Click on it to view its details. Select **1.0.0** in the version dropdown. -Select the **hello-universe** pack. The editor appears. Change the `replicas` field to `3` on line `15`. Click on -**Confirm Updates**. The editor closes. +Select the **hello-universe** pack. Change the `replicas` field on line `15` to `3`. Click on **Confirm Updates**. The +editor is closed. Click on **Save Changes** to confirm the changes you have made to your profile. -Navigate to the left **Main Menu** and select **Clusters**. Filter for the with the **service:hello-universe-frontend** -tag. Palette indicates that the cluster associated with the cluster profile you updated has updates available. +Navigate to the left **Main Menu** and select **Clusters**. Palette indicates that the cluster associated with the +cluster profile you edited has updates available. ![Image that shows the pending updates ](/getting-started/aws/getting-started_update-k8s-cluster_pending-update-clusters-view.webp) @@ -236,9 +228,10 @@ Select this cluster to open its **Overview** tab. Click on **Updates** to begin ![Image that shows the Updates button](/getting-started/aws/getting-started_update-k8s-cluster_updates-available-button-cluster-overview.webp) -A dialog appears which shows the changes made in this update. Review the changes and ensure the only change is the -`replicas` field value. The pending update removes your cluster override and sets the `replicas` field to `3`. At this -point, you can choose to apply the pending changes or keep it by modifying the right-hand side of the dialog. +A dialog appears, showing a summary of packs changed. Select **Review changes in Editor** to review your changes. Ensure +the only change is the `replicas` field value. The pending update removes your cluster override and sets the `replicas` +field to `3`. At this point, you can choose to apply the pending changes or make additional changes by modifying the +**Pending Configuration** pane on the right side of the editor. ![Image that shows the available updates dialog ](/getting-started/aws/getting-started_update-k8s-cluster_available-updates-dialog.webp) @@ -247,7 +240,8 @@ Click on **Apply Changes** once you have finished reviewing your changes. Palette updates your cluster according to cluster profile specifications. Once these changes are complete, select the **Workloads** tab. Then, select the **hello-universe** namespace. -Three **ui** pods are available. The cluster profile update is now reflected by your cluster. +Three **ui** pods are available. The cluster profile update is now reflected by your cluster. If your changes are not +displayed, use the **refresh** icon. ## Cluster Observability @@ -282,8 +276,8 @@ selection to remove the cluster profile. ## Wrap-Up In this tutorial, you created deployed cluster profile updates. After the cluster was deployed to AWS, you updated the -cluster profile through three different methods: create a new cluster profile version, update a cluster profile in -place, and cluster profile overrides. After you made your changes, the Hello Universe application functioned as a +cluster profile through three different methods: creating a new cluster profile version, updating a cluster profile in +place, and using cluster profile overrides. After you made your changes, the Hello Universe application functioned as a three-tier application with a REST API backend server. Cluster profiles provide consistency during the cluster creation process, as well as when maintaining your clusters. 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 020446c937..3a49df8a92 100644 --- a/docs/docs-content/getting-started/azure/create-cluster-profile.md +++ b/docs/docs-content/getting-started/azure/create-cluster-profile.md @@ -10,9 +10,9 @@ tags: ["getting-started", "azure"] Palette offers profile-based management for Kubernetes, enabling consistency, repeatability, and operational efficiency 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](../introduction.md#cluster-profiles). +choose the desired Operating System (OS), Kubernetes, Container Network Interfaces (CNIs), and Container Storage +Interfaces (CSIs). You can further customize the stack with add-on application layers. For more information about +cluster profile 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. The concepts you @@ -103,8 +103,6 @@ preset. Replace these values with your own base64 encoded values. The [_hello-universe_](https://github.com/spectrocloud/hello-universe?tab=readme-ov-file#single-load-balancer) repository provides an unencoded token that you can use. -Click on **Confirm Updates**. The manifest editor closes. - Click on **Confirm & Create** to save the manifest. Then, click on **Save Changes** to save this new layer to the cluster profile. diff --git a/docs/docs-content/getting-started/azure/deploy-k8s-cluster.md b/docs/docs-content/getting-started/azure/deploy-k8s-cluster.md index 4f6aae3c10..dcdeba215f 100644 --- a/docs/docs-content/getting-started/azure/deploy-k8s-cluster.md +++ b/docs/docs-content/getting-started/azure/deploy-k8s-cluster.md @@ -38,7 +38,8 @@ To complete this tutorial, you will need the following. The following steps will guide you through deploying the cluster infrastructure. -Navigate to the left **Main Menu** and select **Clusters**. Click on **Create Cluster**. +Navigate to the left **Main Menu** and select **Clusters**. Click on **Create Cluster**. If there are existing clusters, +choose **Add New Cluster**. ![Palette clusters overview page](/getting-started/getting-started_deploy-k8s-cluster_new_cluster.webp) @@ -105,9 +106,9 @@ Navigate to the left **Main Menu** and select **Clusters**. ![Update the cluster](/getting-started/azure/getting-started_deploy-k8s-cluster_create_cluster.webp) -The cluster deployment process can take 15 to 30 min. The deployment time varies depending on the cloud provider, -cluster profile, cluster size, and the node pool configurations provided. You can learn more about the deployment -progress by reviewing the event log. Click on the **Events** tab to view the log. +The cluster deployment process can take 15 to 30 minutes. Deployment time varies depending on the cloud provider, +cluster profile, cluster size, and node pool configurations provided. You can learn more about the deployment progress +by reviewing the event log. Choose your cluster and select the **Events** tab to view the log. ![Update the cluster](/getting-started/azure/getting-started_deploy-k8s-cluster_event_log.webp) diff --git a/docs/docs-content/getting-started/azure/scale-secure-cluster.md b/docs/docs-content/getting-started/azure/scale-secure-cluster.md index d31fda731e..e19df548a0 100644 --- a/docs/docs-content/getting-started/azure/scale-secure-cluster.md +++ b/docs/docs-content/getting-started/azure/scale-secure-cluster.md @@ -10,8 +10,8 @@ tags: ["getting-started", "azure", "tutorial"] Palette has in-built features to help with the automation of Day-2 operations. Upgrading and maintaining a deployed cluster is typically complex because you need to consider any possible impact on service availability. Palette provides -out-of-the-box functionality for upgrades, observability, granular Role Based Access Control (RBAC), backup and security -scans. +out-of-the-box functionality for upgrades, observability, granular Role Based Access Control (RBAC), backup, and +security scans. This tutorial will teach you how to use the Palette UI to perform scale and maintenance tasks on your clusters. You will learn how to create Palette projects and teams, import a cluster profile, safely upgrade the Kubernetes version of a @@ -33,9 +33,9 @@ Additionally, you should install kubectl locally. Use the Kubernetes ## Create Palette Projects Palette projects help you organize and manage cluster resources, providing logical groupings. They also allow you to -manage user access control through Role Based Access Control (RBAC). You can assign users and teams with specific roles -to specific projects. All resources created within a project are scoped to that project and only available to that -project, but a tenant can have multiple projects. +manage user access control through RBAC. You can assign users and teams with specific roles to specific projects. All +resources created within a project are scoped to that project and only available to that project, but a tenant can have +multiple projects. Log in to [Palette](https://console.spectrocloud.com). @@ -408,18 +408,18 @@ Switch back to Palette in your web browser. Navigate to the left **Main Menu** a cluster profile deployed to your cluster, named `azure-profile`. Ensure that the **1.1.0** version is selected. Click on the **hellouniverse 1.2.0** layer. The manifest editor appears. Set the -`manifests.hello-universe.ui.useTolerations` field on line 20 to `true`. Then, set the -`manifests.hello-universe.ui.effect` field on line 22 to `NoExecute`. This toleration describes that the UI pods of -Hello Universe will tolerate the taint with the key `app`, value `ui` and effect `NoExecute`. The tolerations of the UI +`manifests.hello-universe.ui.useTolerations` field on line 19 to `true`. Then, set the +`manifests.hello-universe.ui.effect` field on line 21 to `NoExecute`. This toleration describes that the UI pods of +Hello Universe will tolerate the taint with the effect `NoExecute`, key `app`, and value `ui`. The tolerations of the UI pods should be as below. ```yaml ui: useTolerations: true tolerations: - effect: NoExecute - key: app - value: ui + effect: NoExecute + key: app + value: ui ``` Click on **Confirm Updates**. The manifest editor closes. Then, click on **Save Changes** to persist your changes. 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 13d87a3c66..5db7bf1408 100644 --- a/docs/docs-content/getting-started/azure/update-k8s-cluster.md +++ b/docs/docs-content/getting-started/azure/update-k8s-cluster.md @@ -64,17 +64,12 @@ panel. ![Image that shows how to add a cluster tag](/getting-started/azure/getting-started_update-k8s-cluster_add-service-tag.webp) -Navigate to the left **Main Menu** and select **Clusters** to view your deployed clusters. Click on **Add Filter**, then -select the **Add custom filter** option. - -Use the drop-down boxes to fill in the values of the filter. Select **Tags** in the left-hand **drop-down Menu**. Select -**is** in the middle **drop-down Menu**. Fill in **service:hello-universe-frontend** in the right-hand input box. - -Click on **Apply Filter**. +Navigate to the left **Main Menu** and select **Clusters** to view your deployed clusters. Click the **filter** icon to +expand the **All Filters** pane, and below **Tags**, enter **service:hello-universe-frontend**. ![Image that shows how to add a frontend service filter](/getting-started/azure/getting-started_update-k8s-cluster_apply-frontend-filter.webp) -Once you apply the filter, only the `azure-cluster` with this tag is displayed. +Only the `azure-cluster` with this tag is displayed. ## Version Cluster Profiles @@ -117,8 +112,7 @@ Click on **Confirm & Create**. The manifest editor closes. Click on **Save Changes** to finish the configuration of this cluster profile version. -Navigate to the left **Main Menu** and select **Clusters**. Filter for the cluster with the -**service:hello-universe-frontend** tag. Select it to view its **Overview** tab. +Navigate to the left **Main Menu** and select **Clusters**. Select the `azure-cluster` to view its **Overview** tab. Select the **Profile** tab of this cluster. You can select a new version of your cluster profile by using the version dropdown. @@ -138,7 +132,7 @@ backups before you make any cluster profile version changes in your production e ::: Palette now makes the required changes to your cluster according to the specifications of the configured cluster profile -version. Once your changes have completed, Palette marks your layers with the green status indicator. The Kubecost pack +version. Once your changes are applied, Palette marks your layers with the green status indicator. The Kubecost pack will be successfully deployed. ![Image that shows completed cluster profile updates](/getting-started/azure/getting-started_update-k8s-cluster_completed-cluster-updates.webp) @@ -182,17 +176,16 @@ the time to recovery in the event of an incident. The process to roll back to a previous version is identical to the process for applying a new version. -Navigate to the left **Main Menu** and select **Clusters**. Filter for the cluster with the -**service:hello-universe-frontend** tag. Select it to view its **Overview** tab. +Navigate to the left **Main Menu** and select **Clusters**. Select the `azure-cluster` to view its **Overview** tab. Select the **Profile** tab. This cluster is currently deployed using cluster profile version **1.1.0**. Select the -option **1.0.0** in the version dropdown. This process is the reverse of what you have done in the previous section, +option **1.0.0** in the version dropdown. This process is the reverse of what you did in the previous section, [Version Cluster Profiles](#version-cluster-profiles). Click on **Save** to confirm your changes. Palette now makes the changes required for the cluster to return to the state specified in version **1.0.0** of your -cluster profile. Once your changes have completed, Palette marks your layers with the green status indicator. +cluster profile. Once your changes are applied, Palette marks your layers with the green status indicator. ![Cluster details page with service URL highlighted](/getting-started/azure/getting-started_update-k8s-cluster_rollback.webp) @@ -204,11 +197,10 @@ choose to apply your changes at a convenient time. The previous state of the cluster profile will not be saved once it is overwritten. -Navigate to the left **Main Menu** and select **Clusters**. Filter for the cluster with the tag -**service:hello-universe-frontend**. Select it to view its **Overview** tab. +Navigate to the left **Main Menu** and select **Clusters**. Select the `azure-cluster` to view its **Overview** tab. -Select the **Profile** tab. Then, select the **hello-universe** pack. Change the `replicas` field to `2` on line `15`. -Click on **Save**. The editor closes. +Select the **Profile** tab. Then, select the **hello-universe** pack. Change the `replicas` field on line `15` to `2` +and **Save** your changes. The editor is closed. This cluster now contains an override over its cluster profile. Palette uses the configuration you have just provided for the single cluster over its cluster profile and begins making the appropriate changes. @@ -216,20 +208,20 @@ for the single cluster over its cluster profile and begins making the appropriat Once these changes are complete, select the **Workloads** tab. Then, select the **hello-universe** namespace. Two **ui** pods are available, instead of the one specified by your cluster profile. Your override has been successfully -applied. +applied. If your changes are not displayed, use the **refresh** icon. Navigate to the left **Main Menu** and select **Profiles** to view the cluster profile page. Find the cluster profile corresponding to your _hello-universe-frontend_ cluster, named `azure-profile`. Click on it to view its details. Select **1.0.0** in the version dropdown. -Select the **hello-universe** pack. The editor appears. Change the `replicas` field to `3` on line `15`. Click on -**Confirm Updates**. The editor closes. +Select the **hello-universe** pack. Change the `replicas` field on line `15` to `3`. Click on **Confirm Updates**. The +editor is closed. Click on **Save Changes** to confirm the changes you have made to your profile. -Navigate to the left **Main Menu** and select **Clusters**. Filter for the with the **service:hello-universe-frontend** -tag. Palette indicates that the cluster associated with the cluster profile you updated has updates available. +Navigate to the left **Main Menu** and select **Clusters**. Palette indicates that the cluster associated with the +cluster profile you edited has updates available. ![Image that shows the pending updates ](/getting-started/azure/getting-started_update-k8s-cluster_pending-update-clusters-view.webp) @@ -237,11 +229,10 @@ Select this cluster to open its **Overview** tab. Click on **Updates** to begin ![Image that shows the Updates button](/getting-started/azure/getting-started_update-k8s-cluster_updates-available-button-cluster-overview.webp) -A dialog appears which shows the changes made in this update. Click on **Review changes in Editor**. As previously, -Palette displays the changes, with the current configuration on the left and the incoming configuration on the right. - -Review the changes and ensure the only change is the `replicas` field value. You can choose to maintain your cluster -override or apply the incoming cluster profile update. +A dialog appears, showing a summary of packs changed. Select **Review changes in Editor** to review your changes. Ensure +the only change is the `replicas` field value. The pending update removes your cluster override and sets the `replicas` +field to `3`. At this point, you can choose to apply the pending changes or make additional changes by modifying the +**Pending Configuration** pane on the right side of the editor. ![Image that shows the available updates dialog ](/getting-started/azure/getting-started_update-k8s-cluster_available-updates-dialog.webp) @@ -250,7 +241,8 @@ Click on **Apply Changes** once you have finished reviewing your changes. This r Palette updates your cluster according to cluster profile specifications. Once these changes are complete, select the **Workloads** tab. Then, select the **hello-universe** namespace. -Three **ui** pods are available. The cluster profile update is now reflected by your cluster. +Three **ui** pods are available. The cluster profile update is now reflected by your cluster. If your changes are not +displayed, use the **refresh** icon. ## Cluster Observability @@ -285,8 +277,8 @@ selection to remove the cluster profile. ## Wrap-Up In this tutorial, you created deployed cluster profile updates. After the cluster was deployed to Azure, you updated the -cluster profile through three different methods: create a new cluster profile version, update a cluster profile in -place, and cluster profile overrides. After you made your changes, the Hello Universe application functioned as a +cluster profile through three different methods: creating a new cluster profile version, updating a cluster profile in +place, and using cluster profile overrides. After you made your changes, the Hello Universe application functioned as a three-tier application with a REST API backend server. Cluster profiles provide consistency during the cluster creation process, as well as when maintaining your clusters. 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 a63d7c82de..b1c069f7f8 100644 --- a/docs/docs-content/getting-started/gcp/create-cluster-profile.md +++ b/docs/docs-content/getting-started/gcp/create-cluster-profile.md @@ -10,9 +10,9 @@ tags: ["getting-started", "gcp"] Palette offers profile-based management for Kubernetes, enabling consistency, repeatability, and operational efficiency 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](../introduction.md#cluster-profiles). +choose the desired Operating System (OS), Kubernetes, Container Network Interfaces (CNIs), and Container Storage +Interfaces (CSIs). You can further customize the stack with add-on application layers. For more information about +cluster profile 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. The concepts you @@ -104,8 +104,6 @@ preset. Replace these values with your own base64 encoded values. The [_hello-universe_](https://github.com/spectrocloud/hello-universe?tab=readme-ov-file#single-load-balancer) repository provides an unencoded token that you can use. -Click on **Confirm Updates**. The manifest editor closes. - Click on **Confirm & Create** to save the manifest. Then, click on **Save Changes** to save this new layer to the cluster profile. diff --git a/docs/docs-content/getting-started/gcp/deploy-k8s-cluster.md b/docs/docs-content/getting-started/gcp/deploy-k8s-cluster.md index 3ed182ef53..b4a72d47e5 100644 --- a/docs/docs-content/getting-started/gcp/deploy-k8s-cluster.md +++ b/docs/docs-content/getting-started/gcp/deploy-k8s-cluster.md @@ -38,7 +38,8 @@ To complete this tutorial, you will need the following. The following steps will guide you through deploying the cluster infrastructure. -Navigate to the left **Main Menu** and select **Clusters**. Click on **Create Cluster**. +Navigate to the left **Main Menu** and select **Clusters**. Click on **Create Cluster**. If there are existing clusters, +choose **Add New Cluster**. ![Palette clusters overview page](/getting-started/getting-started_deploy-k8s-cluster_new_cluster.webp) @@ -106,9 +107,9 @@ Navigate to the left **Main Menu** and select **Clusters**. ![Update the cluster](/getting-started/gcp/getting-started_deploy-k8s-cluster_new_cluster.webp) -The cluster deployment process can take 15 to 30 min. The deployment time varies depending on the cloud provider, -cluster profile, cluster size, and the node pool configurations provided. You can learn more about the deployment -progress by reviewing the event log. Click on the **Events** tab to view the log. +The cluster deployment process can take 15 to 30 minutes. Deployment time varies depending on the cloud provider, +cluster profile, cluster size, and node pool configurations provided. You can learn more about the deployment progress +by reviewing the event log. Choose your cluster and select the **Events** tab to view the log. ![Update the cluster](/getting-started/gcp/getting-started_deploy-k8s-cluster_event_log.webp) diff --git a/docs/docs-content/getting-started/gcp/scale-secure-cluster.md b/docs/docs-content/getting-started/gcp/scale-secure-cluster.md index 9154008d0a..e0aae63af2 100644 --- a/docs/docs-content/getting-started/gcp/scale-secure-cluster.md +++ b/docs/docs-content/getting-started/gcp/scale-secure-cluster.md @@ -10,8 +10,8 @@ tags: ["getting-started", "gcp", "tutorial"] Palette has in-built features to help with the automation of Day-2 operations. Upgrading and maintaining a deployed cluster is typically complex because you need to consider any possible impact on service availability. Palette provides -out-of-the-box functionality for upgrades, observability, granular Role Based Access Control (RBAC), backup and security -scans. +out-of-the-box functionality for upgrades, observability, granular Role Based Access Control (RBAC), backup, and +security scans. This tutorial will teach you how to use the Palette UI to perform scale and maintenance tasks on your clusters. You will learn how to create Palette projects and teams, import a cluster profile, safely upgrade the Kubernetes version of a @@ -33,9 +33,9 @@ Additionally, you should install kubectl locally. Use the Kubernetes ## Create Palette Projects Palette projects help you organize and manage cluster resources, providing logical groupings. They also allow you to -manage user access control through Role Based Access Control (RBAC). You can assign users and teams with specific roles -to specific projects. All resources created within a project are scoped to that project and only available to that -project, but a tenant can have multiple projects. +manage user access control through RBAC. You can assign users and teams with specific roles to specific projects. All +resources created within a project are scoped to that project and only available to that project, but a tenant can have +multiple projects. Log in to [Palette](https://console.spectrocloud.com). @@ -408,18 +408,18 @@ Switch back to Palette in your web browser. Navigate to the left **Main Menu** a cluster profile deployed to your cluster, named `gcp-profile`. Ensure that the **1.1.0** version is selected. Click on the **hellouniverse 1.2.0** layer. The manifest editor appears. Set the -`manifests.hello-universe.ui.useTolerations` field on line 20 to `true`. Then, set the -`manifests.hello-universe.ui.effect` field on line 22 to `NoExecute`. This toleration describes that the UI pods of -Hello Universe will tolerate the taint with the key `app`, value `ui` and effect `NoExecute`. The tolerations of the UI +`manifests.hello-universe.ui.useTolerations` field on line 19 to `true`. Then, set the +`manifests.hello-universe.ui.effect` field on line 21 to `NoExecute`. This toleration describes that the UI pods of +Hello Universe will tolerate the taint with the effect `NoExecute`, key `app`, and value `ui`. The tolerations of the UI pods should be as below. ```yaml ui: useTolerations: true tolerations: - effect: NoExecute - key: app - value: ui + effect: NoExecute + key: app + value: ui ``` Click on **Confirm Updates**. The manifest editor closes. Then, click on **Save Changes** to persist your changes. 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 2478a4e09c..b23b67c619 100644 --- a/docs/docs-content/getting-started/gcp/update-k8s-cluster.md +++ b/docs/docs-content/getting-started/gcp/update-k8s-cluster.md @@ -64,17 +64,12 @@ panel. ![Image that shows how to add a cluster tag](/getting-started/gcp/getting-started_update-k8s-cluster_add-service-tag.webp) -Navigate to the left **Main Menu** and select **Clusters** to view your deployed clusters. Click on **Add Filter**, then -select the **Add custom filter** option. - -Use the drop-down boxes to fill in the values of the filter. Select **Tags** in the left-hand **drop-down Menu**. Select -**is** in the middle **drop-down Menu**. Fill in **service:hello-universe-frontend** in the right-hand input box. - -Click on **Apply Filter**. +Navigate to the left **Main Menu** and select **Clusters** to view your deployed clusters. Click the **filter** icon to +expand the **All Filters** pane, and below **Tags**, enter **service:hello-universe-frontend**. ![Image that shows how to add a frontend service filter](/getting-started/gcp/getting-started_update-k8s-cluster_apply-frontend-filter.webp) -Once you apply the filter, only the `gcp-cluster` with this tag is displayed. +Only the `gcp-cluster` with this tag is displayed. ## Version Cluster Profiles @@ -117,8 +112,7 @@ Click on **Confirm & Create**. The manifest editor closes. Click on **Save Changes** to finish the configuration of this cluster profile version. -Navigate to the left **Main Menu** and select **Clusters**. Filter for the cluster with the -**service:hello-universe-frontend** tag. Select it to view its **Overview** tab. +Navigate to the left **Main Menu** and select **Clusters**. Select the `gcp-cluster` to view its **Overview** tab. Select the **Profile** tab of this cluster. You can select a new version of your cluster profile by using the version dropdown. @@ -138,7 +132,7 @@ backups before you make any cluster profile version changes in your production e ::: Palette now makes the required changes to your cluster according to the specifications of the configured cluster profile -version. Once your changes have completed, Palette marks your layers with the green status indicator. The Kubecost pack +version. Once your changes are applied, Palette marks your layers with the green status indicator. The Kubecost pack will be successfully deployed. ![Image that shows completed cluster profile updates](/getting-started/gcp/getting-started_update-k8s-cluster_completed-cluster-updates.webp) @@ -181,17 +175,16 @@ the time to recovery in the event of an incident. The process to roll back to a previous version is identical to the process for applying a new version. -Navigate to the left **Main Menu** and select **Clusters**. Filter for the cluster with the -**service:hello-universe-frontend** tag. Select it to view its **Overview** tab. +Navigate to the left **Main Menu** and select **Clusters**. Select the `gcp-cluster` to view its **Overview** tab. Select the **Profile** tab. This cluster is currently deployed using cluster profile version **1.1.0**. Select the -option **1.0.0** in the version dropdown. This process is the reverse of what you have done in the previous section, +option **1.0.0** in the version dropdown. This process is the reverse of what you did in the previous section, [Version Cluster Profiles](#version-cluster-profiles). Click on **Save** to confirm your changes. Palette now makes the changes required for the cluster to return to the state specified in version **1.0.0** of your -cluster profile. Once your changes have completed, Palette marks your layers with the green status indicator. +cluster profile. Once your changes are applied, Palette marks your layers with the green status indicator. ![Cluster details page with service URL highlighted](/getting-started/gcp/getting-started_deploy-k8s-cluster_service_url.webp) @@ -203,11 +196,10 @@ choose to apply your changes at a convenient time. The previous state of the cluster profile will not be saved once it is overwritten. -Navigate to the left **Main Menu** and select **Clusters**. Filter for the cluster with the tag -**service:hello-universe-frontend**. Select it to view its **Overview** tab. +Navigate to the left **Main Menu** and select **Clusters**. Select the `gcp-cluster` to view its **Overview** tab. -Select the **Profiles** tab. Then, select the **hello-universe** pack. Change the `replicas` field to `2` on line `15`. -Click on **Save**. The editor closes. +Select the **Profile** tab. Then, select the **hello-universe** pack. Change the `replicas` field on line `15` to `2` +and **Save** your changes. The editor is closed. This cluster now contains an override over its cluster profile. Palette uses the configuration you have just provided for the single cluster over its cluster profile and begins making the appropriate changes. @@ -215,15 +207,15 @@ for the single cluster over its cluster profile and begins making the appropriat Once these changes are complete, select the **Workloads** tab. Then, select the **hello-universe** namespace. Two **ui** pods are available, instead of the one specified by your cluster profile. Your override has been successfully -applied. +applied. If your changes are not displayed, use the **refresh** icon. Navigate to the left **Main Menu** and select **Profiles** to view the cluster profile page. Find the cluster profile corresponding to your _hello-universe-frontend_ cluster, named `gcp-profile`. Click on it to view its details. Select **1.0.0** in the version dropdown. -Select the **hello-universe** pack. The editor appears. Change the `replicas` field to `3` on line `15`. Click on -**Confirm Updates**. The editor closes. +Select the **hello-universe** pack. Change the `replicas` field on line `15` to `3`. Click on **Confirm Updates**. The +editor is closed. Click on **Save Changes** to confirm the changes you have made to your profile. @@ -237,9 +229,10 @@ Select this cluster to open its **Overview** tab. Click on **Updates** to begin ![Image that shows the Updates button](/getting-started/gcp/getting-started_update-k8s-cluster_updates-available-button-cluster-overview.webp) -A dialog appears which shows the changes made in this update. Review the changes and ensure the only change is the -`replicas` field value. The pending update removes your cluster override and sets the `replicas` field to `3`. At this -point, you can choose to apply the pending changes or keep it by modifying the right-hand side of the dialog. +A dialog appears, showing a summary of packs changed. Select **Review changes in Editor** to review your changes. Ensure +the only change is the `replicas` field value. The pending update removes your cluster override and sets the `replicas` +field to `3`. At this point, you can choose to apply the pending changes or make additional changes by modifying the +**Pending Configuration** pane on the right side of the editor. ![Image that shows the available updates dialog ](/getting-started/gcp/getting-started_update-k8s-cluster_available-updates-dialog.webp) @@ -248,7 +241,8 @@ Click on **Apply Changes** once you have finished reviewing your changes. Palette updates your cluster according to cluster profile specifications. Once these changes are complete, select the **Workloads** tab. Then, select the **hello-universe** namespace. -Three **ui** pods are available. The cluster profile update is now reflected by your cluster. +Three **ui** pods are available. The cluster profile update is now reflected by your cluster. If your changes are not +displayed, use the **refresh** icon. ## Cluster Observability @@ -282,9 +276,9 @@ selection to remove the cluster profile. ## Wrap-Up -In this tutorial, you created deployed cluster profile updates. After the cluster was deployed to AWS, you updated the -cluster profile through three different methods: create a new cluster profile version, update a cluster profile in -place, and cluster profile overrides. After you made your changes, the Hello Universe application functioned as a +In this tutorial, you created deployed cluster profile updates. After the cluster was deployed to GCP, you updated the +cluster profile through three different methods: creating a new cluster profile version, updating a cluster profile in +place, and using cluster profile overrides. After you made your changes, the Hello Universe application functioned as a three-tier application with a REST API backend server. Cluster profiles provide consistency during the cluster creation process, as well as when maintaining your clusters. 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 6d106cb062..ad27a732a0 100644 --- a/docs/docs-content/getting-started/vmware/create-cluster-profile.md +++ b/docs/docs-content/getting-started/vmware/create-cluster-profile.md @@ -10,9 +10,9 @@ tags: ["getting-started", "vmware"] Palette offers profile-based management for Kubernetes, enabling consistency, repeatability, and operational efficiency 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](../introduction.md#cluster-profiles). +choose the desired Operating System (OS), Kubernetes, Container Network Interfaces (CNIs), and Container Storage +Interfaces (CSIs). You can further customize the stack with add-on application layers. For more information about +cluster profile 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. The concepts you @@ -129,8 +129,6 @@ preset. Replace these values with your own base64 encoded values. The [_hello-universe_](https://github.com/spectrocloud/hello-universe?tab=readme-ov-file#single-load-balancer) repository provides an unencoded token that you can use. -Click on **Confirm Updates**. The manifest editor closes. - Click on **Confirm & Create** to save the manifest. Then, click on **Save Changes** to save this new layer to the cluster profile. diff --git a/docs/docs-content/getting-started/vmware/deploy-k8s-cluster.md b/docs/docs-content/getting-started/vmware/deploy-k8s-cluster.md index 28b6d8437c..7b15deb9ad 100644 --- a/docs/docs-content/getting-started/vmware/deploy-k8s-cluster.md +++ b/docs/docs-content/getting-started/vmware/deploy-k8s-cluster.md @@ -41,7 +41,8 @@ To complete this tutorial, you will need the following. The following steps will guide you through deploying the cluster infrastructure. -Navigate to the left **Main Menu** and select **Clusters**. Click on **Create Cluster**. +Navigate to the left **Main Menu** and select **Clusters**. Click on **Create Cluster**. If there are existing clusters, +choose **Add New Cluster**. ![Palette clusters overview page](/getting-started/getting-started_deploy-k8s-cluster_new_cluster.webp) @@ -106,9 +107,9 @@ Navigate to the left **Main Menu** and select **Clusters**. ![Update the cluster](/getting-started/vmware/getting-started_deploy-k8s-cluster_new_cluster.webp) -The cluster deployment process can take 15 to 30 min. The deployment time varies depending on the cloud provider, -cluster profile, cluster size, and the node pool configurations provided. You can learn more about the deployment -progress by reviewing the event log. Click on the **Events** tab to view the log. +The cluster deployment process can take 15 to 30 minutes. Deployment time varies depending on the cloud provider, +cluster profile, cluster size, and node pool configurations provided. You can learn more about the deployment progress +by reviewing the event log. Choose your cluster and select the **Events** tab to view the log. ![Update the cluster](/getting-started/vmware/getting-started_deploy-k8s-cluster_event_log.webp) diff --git a/docs/docs-content/getting-started/vmware/scale-secure-cluster.md b/docs/docs-content/getting-started/vmware/scale-secure-cluster.md index 3b25311dcc..0d8f2c7cd2 100644 --- a/docs/docs-content/getting-started/vmware/scale-secure-cluster.md +++ b/docs/docs-content/getting-started/vmware/scale-secure-cluster.md @@ -10,8 +10,8 @@ tags: ["getting-started", "vmware", "tutorial"] Palette has in-built features to help with the automation of Day-2 operations. Upgrading and maintaining a deployed cluster is typically complex because you need to consider any possible impact on service availability. Palette provides -out-of-the-box functionality for upgrades, observability, granular Role Based Access Control (RBAC), backup and security -scans. +out-of-the-box functionality for upgrades, observability, granular Role Based Access Control (RBAC), backup, and +security scans. This tutorial will teach you how to use the Palette UI to perform scale and maintenance tasks on your clusters. You will learn how to create Palette projects and teams, import a cluster profile, safely upgrade the Kubernetes version of a @@ -36,9 +36,9 @@ Additionally, you should install kubectl locally. Use the Kubernetes ## Create Palette Projects Palette projects help you organize and manage cluster resources, providing logical groupings. They also allow you to -manage user access control through Role Based Access Control (RBAC). You can assign users and teams with specific roles -to specific projects. All resources created within a project are scoped to that project and only available to that -project, but a tenant can have multiple projects. +manage user access control through RBAC. You can assign users and teams with specific roles to specific projects. All +resources created within a project are scoped to that project and only available to that project, but a tenant can have +multiple projects. Log in to [Palette](https://console.spectrocloud.com). @@ -423,18 +423,18 @@ Switch back to Palette in your web browser. Navigate to the left **Main Menu** a cluster profile deployed to your cluster, named `vmware-profile`. Ensure that the **1.1.0** version is selected. Click on the **hellouniverse 1.2.0** layer. The manifest editor appears. Set the -`manifests.hello-universe.ui.useTolerations` field on line 20 to `true`. Then, set the -`manifests.hello-universe.ui.effect` field on line 22 to `NoExecute`. This toleration describes that the UI pods of -Hello Universe will tolerate the taint with the key `app`, value `ui` and effect `NoExecute`. The tolerations of the UI +`manifests.hello-universe.ui.useTolerations` field on line 19 to `true`. Then, set the +`manifests.hello-universe.ui.effect` field on line 21 to `NoExecute`. This toleration describes that the UI pods of +Hello Universe will tolerate the taint with the effect `NoExecute`, key `app`, and value `ui`. The tolerations of the UI pods should be as below. ```yaml ui: useTolerations: true tolerations: - effect: NoExecute - key: app - value: ui + effect: NoExecute + key: app + value: ui ``` Click on **Confirm Updates**. The manifest editor closes. Then, click on **Save Changes** to persist your changes. 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 7e9fa10d36..668319df46 100644 --- a/docs/docs-content/getting-started/vmware/update-k8s-cluster.md +++ b/docs/docs-content/getting-started/vmware/update-k8s-cluster.md @@ -64,17 +64,12 @@ panel. ![Image that shows how to add a cluster tag](/getting-started/vmware/getting-started_update-k8s-cluster_add-service-tag.webp) -Navigate to the left **Main Menu** and select **Clusters** to view your deployed clusters. Click on **Add Filter**, then -select the **Add custom filter** option. - -Use the drop-down boxes to fill in the values of the filter. Select **Tags** in the left-hand **drop-down Menu**. Select -**is** in the middle **drop-down Menu**. Fill in **service:hello-universe-frontend** in the right-hand input box. - -Click on **Apply Filter**. +Navigate to the left **Main Menu** and select **Clusters** to view your deployed clusters. Click the **filter** icon to +expand the **All Filters** pane, and below **Tags**, enter **service:hello-universe-frontend**. ![Image that shows how to add a frontend service filter](/getting-started/vmware/getting-started_update-k8s-cluster_apply-frontend-filter.webp) -Once you apply the filter, only the `vmware-cluster` with this tag is displayed. +Only the `vmware-cluster` with this tag is displayed. ## Version Cluster Profiles @@ -117,8 +112,7 @@ Click on **Confirm & Create**. The manifest editor closes. Click on **Save Changes** to finish the configuration of this cluster profile version. -Navigate to the left **Main Menu** and select **Clusters**. Filter for the cluster with the -**service:hello-universe-frontend** tag. Select it to view its **Overview** tab. +Navigate to the left **Main Menu** and select **Clusters**. Select the `vmware-cluster` to view its **Overview** tab. Select the **Profile** tab of this cluster. You can select a new version of your cluster profile by using the version dropdown. @@ -138,7 +132,7 @@ backups before you make any cluster profile version changes in your production e ::: Palette now makes the required changes to your cluster according to the specifications of the configured cluster profile -version. Once your changes have completed, Palette marks your layers with the green status indicator. The Kubecost pack +version. Once your changes are applied, Palette marks your layers with the green status indicator. The Kubecost pack will be successfully deployed. ![Image that shows completed cluster profile updates](/getting-started/vmware/getting-started_update-k8s-cluster_completed-cluster-updates.webp) @@ -183,11 +177,10 @@ the time to recovery in the event of an incident. The process to roll back to a previous version is identical to the process for applying a new version. -Navigate to the left **Main Menu** and select **Clusters**. Filter for the cluster with the -**service:hello-universe-frontend** tag. Select it to view its **Overview** tab. +Navigate to the left **Main Menu** and select **Clusters**. Select the `vmware-cluster` to view its **Overview** tab. Select the **Profile** tab. This cluster is currently deployed using cluster profile version **1.1.0**. Select the -option **1.0.0** in the version dropdown. This process is the reverse of what you have done in the previous section, +option **1.0.0** in the version dropdown. This process is the reverse of what you did in the previous section, [Version Cluster Profiles](#version-cluster-profiles). Click on **Review & Save** to confirm your changes. The **Changes Summary** dialog appears again. @@ -198,7 +191,7 @@ application configuration. Click on **Apply Changes**. Select the **Overview** tab. Palette now makes the changes required for the cluster to return to the state specified in version **1.0.0** of your -cluster profile. Once your changes have completed, Palette marks your layers with the green status indicator. +cluster profile. Once your changes are applied, Palette marks your layers with the green status indicator. ![Cluster details page](/getting-started/vmware/getting-started_update-k8s-cluster_cluster-details.webp) @@ -210,11 +203,10 @@ choose to apply your changes at a convenient time. The previous state of the cluster profile will not be saved once it is overwritten. -Navigate to the left **Main Menu** and select **Clusters**. Filter for the cluster with the tag -**service:hello-universe-frontend**. Select it to view its **Overview** tab. +Navigate to the left **Main Menu** and select **Clusters**. Select the `vmware-cluster` to view its **Overview** tab. -Select the **Profiles** tab. Then, select the **hello-universe** pack. Change the `replicas` field to `2` on line `15`. -Click on **Save**. The editor closes. +Select the **Profile** tab. Then, select the **hello-universe** pack. Change the `replicas` field on line `15` to `2` +and **Save** your changes. The editor is closed. This cluster now contains an override over its cluster profile. Palette uses the configuration you have just provided for the single cluster over its cluster profile and begins making the appropriate changes. @@ -222,15 +214,15 @@ for the single cluster over its cluster profile and begins making the appropriat Once these changes are complete, select the **Workloads** tab. Then, select the **hello-universe** namespace. Two **ui** pods are available, instead of the one specified by your cluster profile. Your override has been successfully -applied. +applied. If your changes are not displayed, use the **refresh** icon. Navigate to the left **Main Menu** and select **Profiles** to view the cluster profile page. Find the cluster profile corresponding to your _hello-universe-frontend_ cluster, named `vmware-profile`. Click on it to view its details. Select **1.0.0** in the version dropdown. -Select the **hello-universe** pack. The editor appears. Change the `replicas` field to `3` on line `15`. Click on -**Confirm Updates**. The editor closes. +Select the **hello-universe** pack. Change the `replicas` field on line `15` to `3`. Click on **Confirm Updates**. The +editor is closed. Click on **Save Changes** to confirm the changes you have made to your profile. @@ -244,9 +236,10 @@ Select this cluster to open its **Overview** tab. Click on **Updates** to begin ![Image that shows the Updates button](/getting-started/vmware/getting-started_update-k8s-cluster_updates-available-button-cluster-overview.webp) -A dialog appears which shows the changes made in this update. Review the changes and ensure the only change is the -`replicas` field value. The pending update removes your cluster override and sets the `replicas` field to `3`. At this -point, you can choose to apply the pending changes or keep it by modifying the right-hand side of the dialog. +A dialog appears, showing a summary of packs changed. Select **Review changes in Editor** to review your changes. Ensure +the only change is the `replicas` field value. The pending update removes your cluster override and sets the `replicas` +field to `3`. At this point, you can choose to apply the pending changes or make additional changes by modifying the +**Pending Configuration** pane on the right side of the editor. ![Image that shows the available updates dialog ](/getting-started/vmware/getting-started_update-k8s-cluster_available-updates-dialog.webp) @@ -255,7 +248,8 @@ Click on **Confirm updates** once you have finished reviewing your changes. Palette updates your cluster according to cluster profile specifications. Once these changes are complete, select the **Workloads** tab. Then, select the **hello-universe** namespace. -Three **ui** pods are available. The cluster profile update is now reflected by your cluster. +Three **ui** pods are available. The cluster profile update is now reflected by your cluster. If your changes are not +displayed, use the **refresh** icon. ## Cluster Observability @@ -292,9 +286,9 @@ selection to remove the cluster profile. ## Wrap-Up In this tutorial, you created deployed cluster profile updates. After the cluster was deployed to VMware, you updated -the cluster profile through three different methods: create a new cluster profile version, update a cluster profile in -place, and cluster profile overrides. After you made your changes, the Hello Universe application functioned as a -three-tier application with a REST API backend server. +the cluster profile through three different methods: creating a new cluster profile version, updating a cluster profile +in place, and using cluster profile overrides. After you made your changes, the Hello Universe application functioned as +a three-tier application with a REST API backend server. Cluster profiles provide consistency during the cluster creation process, as well as when maintaining your clusters. They can be versioned to keep a record of previously working cluster states, giving you visibility when updating or diff --git a/docs/docs-content/registries-and-packs/registries/oci-registry/add-oci-packs.md b/docs/docs-content/registries-and-packs/registries/oci-registry/add-oci-packs.md index 0d1828f351..da22ef0afd 100644 --- a/docs/docs-content/registries-and-packs/registries/oci-registry/add-oci-packs.md +++ b/docs/docs-content/registries-and-packs/registries/oci-registry/add-oci-packs.md @@ -72,7 +72,7 @@ For guidance on how to add a custom pack to an OCI pack registry, check out the } ``` - ## Add OCI Packs Registry +## Add OCI Packs Registry Use the following steps to add an OCI Packs registry to Palette. Select the tab that corresponds to the type of OCI registry you are adding. diff --git a/docs/docs-content/tutorials/profiles/deploy-pack.md b/docs/docs-content/tutorials/profiles/deploy-pack.md index 13dba8b9d4..ff45c8526f 100644 --- a/docs/docs-content/tutorials/profiles/deploy-pack.md +++ b/docs/docs-content/tutorials/profiles/deploy-pack.md @@ -230,6 +230,10 @@ Review each of the following five files in the **hello-universe-pack** folder. ```json { "addonType": "app services", + "annotations": { + "source": "community", + "contributor": "spectrocloud", + } "cloudTypes": ["all"], "displayName": "Hello Universe", "kubeManifests": ["manifests/hello-universe.yaml"], diff --git a/static/assets/docs/images/getting-started/aws/getting-started_update-k8s-cluster_apply-frontend-filter.webp b/static/assets/docs/images/getting-started/aws/getting-started_update-k8s-cluster_apply-frontend-filter.webp index 9bf322392a..2f1cdb8010 100644 Binary files a/static/assets/docs/images/getting-started/aws/getting-started_update-k8s-cluster_apply-frontend-filter.webp and b/static/assets/docs/images/getting-started/aws/getting-started_update-k8s-cluster_apply-frontend-filter.webp differ diff --git a/static/assets/docs/images/getting-started/azure/getting-started_update-k8s-cluster_apply-frontend-filter.webp b/static/assets/docs/images/getting-started/azure/getting-started_update-k8s-cluster_apply-frontend-filter.webp index 6f7c27afab..fa4460c8d8 100644 Binary files a/static/assets/docs/images/getting-started/azure/getting-started_update-k8s-cluster_apply-frontend-filter.webp and b/static/assets/docs/images/getting-started/azure/getting-started_update-k8s-cluster_apply-frontend-filter.webp differ