Skip to content

Commit

Permalink
docs: added images (#1377)
Browse files Browse the repository at this point in the history
* docs: added images

* docs: added newline

* Apply suggestions from code review

Co-authored-by: Rita Watson <117382432+ritawatson@users.noreply.github.com>

---------

Co-authored-by: Rita Watson <117382432+ritawatson@users.noreply.github.com>
  • Loading branch information
karl-cardenas-coding and ritawatson committed Jun 23, 2023
1 parent 2824d1b commit 8dfa38e
Show file tree
Hide file tree
Showing 6 changed files with 33 additions and 13 deletions.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
5 changes: 5 additions & 0 deletions content/docs/02.5-architecture/01-architecture-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,11 @@ Palette is available in three flexible deployment models:

<br />

![A diagram of Palette deployment models](/architecture_architecture-overview-deployment-models.png)

<br />


## Product Security

At Spectro Cloud, we recognize the importance of robust security measures in today's rapidly evolving digital landscape. As the provider of our cutting-edge SaaS and self-hosted Palette product, our commitment to safeguarding your data and ensuring the integrity of our services is paramount. Learn more about Palette security by reviewing the [Security](/security) section.
Expand Down
1 change: 1 addition & 0 deletions content/docs/04-clusters.md
Original file line number Diff line number Diff line change
Expand Up @@ -285,4 +285,5 @@ Clusters are launched from within Projects in Palette, and they belong to a sing
# Additional Resources

The next section provides details for setting workload clusters in various environments.

<br />
32 changes: 19 additions & 13 deletions content/docs/04-clusters/03-edge.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,13 @@ Palette provisions workload clusters on Edge hosts from the Palette management c
Edge computing brings computing and data storage closer to the source, reducing latency and bandwidth issues that result from central computing and improving overall application performance. Industries such as retail, restaurants, manufacturing, oil and gas, cruise ships, healthcare, and 5G telecommunication providers typically have use cases that require content data and processing to be closer to their applications.


<br />

![A drawing of Edge architecture with humans interacting](/clusters_edge_edge-arch-drawing.png)

<br />



The following are some highlights of the comprehensive Palette Edge Solution:

Expand All @@ -48,40 +55,39 @@ The following are some highlights of the comprehensive Palette Edge Solution:
* Support for pre-provisioned and on-site device registration


<br />

<WarningBox>

Edge is still in active development and is subject to change. Review the Palette [release notes](/release-notes) for updates and changes.
Palette's Edge solution is designed for sites that typically have one or more small devices, such as [Intel NUC](https://www.intel.com/content/www/us/en/products/docs/boards-kits/nuc/what-is-nuc-article.html). An instance of Palette optimized for edge computing is installed in the device along with the operating system and Kubernetes.


</WarningBox>
<br />

<InfoBox>

<br />
Edge is built on top of the open-source project [Kairos](https://kairos.io), which provides a tamper-proof immutable operating system with zero downtime rolling upgrade.

</InfoBox>

Palette manages the installation and all the Day-2 activities, such as scaling, upgrades, and reconfiguration.

# Get Started With Edge
<br />

<WarningBox>

To start with Edge, review the [architecture](/clusters/edge/architecture) and the [lifecycle](/clusters/edge/edge-native-lifecycle) resource to gain a high-level understanding of the Edge components and installation process. Next, become familiar with the [EdgeForge workflow](/clusters/edge/edgeforge-workflow). EdgeForge is the workflow you will use to customize the Edge host installation to match your environment and organizational needs - this includes creating the Edge artifacts for Edge hosts. The last step of the Edge deployment lifecycle is the deployment step. Review the [Deployment](/clusters/edge/site-deployment) guide to understand what it takes to deploy an Edge host.
Edge is still in active development and is subject to change. Review the Palette [release notes](/release-notes) for updates and changes.

# Edge Native

Palette's Edge native solution is designed for sites that typically have one or more small devices, such as [Intel NUC](https://www.intel.com/content/www/us/en/products/docs/boards-kits/nuc/what-is-nuc-article.html). An instance of Palette optimized for edge computing, along with the operating system and Kubernetes, is installed in the device.
</WarningBox>

Palette manages the installation and all the Day-2 activities, such as scaling, upgrades, and reconfiguration.

<br />

<InfoBox>

Edge is built on top of the open-source project [Kairos](https://kairos.io), which provides a tamper-proof immutable operating system with zero downtime rolling upgrade.

</InfoBox>
# Get Started With Edge


To start with Edge, review the [architecture](/clusters/edge/architecture) and the [lifecycle](/clusters/edge/edge-native-lifecycle) resource to gain a high-level understanding of the Edge components and installation process. Next, become familiar with the [EdgeForge workflow](/clusters/edge/edgeforge-workflow). EdgeForge is the workflow you will use to customize the Edge host installation to match your environment and organizational needs - this includes creating the Edge artifacts for Edge hosts. The last step of the Edge deployment lifecycle is the deployment step. Review the [Deployment](/clusters/edge/site-deployment) guide to understand what it takes to deploy an Edge host.

<br />

Expand Down
8 changes: 8 additions & 0 deletions content/docs/09.5-security/10-product-architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,14 @@ Palette supports three architecture models: multi-tenant SaaS, dedicated SaaS, a

- **Self-hosted**: The management plane is hosted in your environment. It can be on-prem VMware vSphere, OpenStack, bare metal, in a public cloud that manages your compute instances, or a managed Kubernetes cluster such as Amazon Elastic Kubernetes Service (EKS), Azure Kubernetes Service (AKS), and Google Kubernetes Engine (GKE).


<br />

![A diagram of Palette deployment models](/architecture_architecture-overview-deployment-models.png)

<br />


Palette’s robust security measures safeguard your data and ensure the integrity of our services. We adhere to industry-leading standards and continuously refine our practices to provide the highest level of security. Palette infrastructure safeguards data in your Kubernetes production environment with its zero-trust architecture, granular Role-Based Access Control (RBAC), immutable Linux distributions ([Kairos](https://kairos.io/)), and hardened clusters and Kubernetes packs.

Palette's security controls ensure data protection in SaaS operation at the management platform level and the [tenant](/glossary-all#tenant) cluster level. To learn more, refer to [SaaS Operation](/security/product-architecture/saas-operation). In self-hosted operation, you must ensure security controls in your environment. Find out more about self-hosted deployment in [Self-Hosted Operation](/security/product-architecture/self-hosted-operation).
Expand Down

0 comments on commit 8dfa38e

Please sign in to comment.