diff --git a/docs/docs-content/architecture/grps-proxy.md b/docs/docs-content/architecture/grps-proxy.md index 3b27e782fc..9c12ae0bf8 100644 --- a/docs/docs-content/architecture/grps-proxy.md +++ b/docs/docs-content/architecture/grps-proxy.md @@ -35,7 +35,7 @@ The following sections provide more information about gRPC and proxies. ## Proxy Without SSL Bump -Because gRPC is based on HTTP/2, any proxy server that supports the [HTTP CONNECT](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/CONNECT) method can be used to forward gRPC traffic. No configuration is required for this scenario. The exception is when the proxy server performs an SSL bump, discussed in the [Proxy With SSL Bump](/architecture/grps-proxy#proxywithsslbump) section. +Because gRPC is based on HTTP/2, any proxy server that supports the [HTTP CONNECT](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/CONNECT) method can be used to forward gRPC traffic. No configuration is required for this scenario. The exception is when the proxy server performs an SSL bump, discussed in the [Proxy With SSL Bump](#proxy-with-ssl-bump) section. :::info diff --git a/docs/docs-content/clusters/cluster-groups/cluster-group-backups.md b/docs/docs-content/clusters/cluster-groups/cluster-group-backups.md index bc90317991..133937d2d2 100644 --- a/docs/docs-content/clusters/cluster-groups/cluster-group-backups.md +++ b/docs/docs-content/clusters/cluster-groups/cluster-group-backups.md @@ -11,7 +11,7 @@ Palette [Virtual Clusters](../palette-virtual-clusters/palette-virtual-clusters. ## Prerequisites -* A project or tenant backup location. Refer to the [cluster backup and restore](../cluster-management/backup-restore/backup-restore.md#clusterbackupandrestore) document to learn how to configure a backup location. +* A project or tenant backup location. Refer to the [cluster backup and restore](../cluster-management/backup-restore/backup-restore.md#get-started) document to learn how to configure a backup location. * Cluster group modification [permissions](../../user-management/palette-rbac/palette-rbac.md). diff --git a/docs/docs-content/clusters/cluster-management/backup-restore/add-backup-location-dynamic.md b/docs/docs-content/clusters/cluster-management/backup-restore/add-backup-location-dynamic.md index 3d61c401bd..d6fcc9584c 100644 --- a/docs/docs-content/clusters/cluster-management/backup-restore/add-backup-location-dynamic.md +++ b/docs/docs-content/clusters/cluster-management/backup-restore/add-backup-location-dynamic.md @@ -8,7 +8,7 @@ tags: ["clusters", "cluster management", "backup"] --- -This guide provides instructions for how to add a backup location in Palette using dynamic access credentials. You use the dynamic access credentials to authenticate Palette with the backup location service provider. Refer to the [Backup Location](backup-restore.md#backuplocation) section to learn more about the supported service providers. +This guide provides instructions for how to add a backup location in Palette using dynamic access credentials. You use the dynamic access credentials to authenticate Palette with the backup location service provider. Refer to the [Backup Location](./backup-restore.md#backup-locations-and-credentials) section to learn more about the supported service providers. Depending on the infrastructure provider, there may be limitations or different prerequisites. diff --git a/docs/docs-content/clusters/cluster-management/backup-restore/backup-restore.md b/docs/docs-content/clusters/cluster-management/backup-restore/backup-restore.md index d1a3617924..efa60f9ca8 100644 --- a/docs/docs-content/clusters/cluster-management/backup-restore/backup-restore.md +++ b/docs/docs-content/clusters/cluster-management/backup-restore/backup-restore.md @@ -23,7 +23,7 @@ To get started with creating a backup, check out the [Add a Backup Location usin :::info -If you are using a workspace, refer to the [Manage Palette Workspace](/workspace/workload-features#managepaletteworkspace) guide to learn more about backup and restore actions for a workspace. +If you are using a workspace, refer to the [Manage Palette Workspace](../../../workspace/workload-features.md) guide to learn more about backup and restore actions for a workspace. ::: diff --git a/docs/docs-content/clusters/cluster-management/cluster-tag-filter/cluster-tag-filter.md b/docs/docs-content/clusters/cluster-management/cluster-tag-filter/cluster-tag-filter.md index 0e852e21f5..dbe746fe8e 100644 --- a/docs/docs-content/clusters/cluster-management/cluster-tag-filter/cluster-tag-filter.md +++ b/docs/docs-content/clusters/cluster-management/cluster-tag-filter/cluster-tag-filter.md @@ -15,20 +15,20 @@ To get started with an attribute access control through tags, check out the [Cre - [Cluster Resource Filter](create-add-filter.md) -- [Create Resource Filter](create-add-filter.md#createresourcefilter) +- [Create Resource Filter](create-add-filter.md#create-resource-filter) -- [Add Resource Role](create-add-filter.md#addresourcerole) +- [Add Resource Role](create-add-filter.md#add-resource-role) - [Palette Resource Roles](../../../user-management/palette-rbac/resource-scope-roles-permissions.md) -- [Palette Global Resource Roles](../../../user-management/palette-rbac/resource-scope-roles-permissions.md#paletteglobalresourceroles) +- [Palette Global Resource Roles](../../../user-management/palette-rbac/resource-scope-roles-permissions.md#palette-global-resource-roles) -- [Palette Custom Resource Roles](../../../user-management/palette-rbac/resource-scope-roles-permissions.md#palettecustomresourceroles) +- [Palette Custom Resource Roles](../../../user-management/palette-rbac/resource-scope-roles-permissions.md#palette-custom-resource-roles) -- [Create Custom Role](../../../user-management/new-user.md#createcustomrole) +- [Create Custom Role](../../../user-management/new-user.md#create-custom-role) -- [Create New User in Palette](../../../user-management/new-user.md#createanewuser) +- [Create New User in Palette](../../../user-management/new-user.md#create-a-new-user) diff --git a/docs/docs-content/clusters/cluster-management/cluster-tag-filter/create-add-filter.md b/docs/docs-content/clusters/cluster-management/cluster-tag-filter/create-add-filter.md index 2fcc4f7dec..49a46d4d41 100644 --- a/docs/docs-content/clusters/cluster-management/cluster-tag-filter/create-add-filter.md +++ b/docs/docs-content/clusters/cluster-management/cluster-tag-filter/create-add-filter.md @@ -47,17 +47,17 @@ Upon creating a filter, a display message will pop up to confirm the successful ## Add Resource Role -You can assign the resource filter created, in combination with roles, to a [user](../../../user-management/new-user.md#createanewuser) to enforce access restriction. Palette provisions two types of roles: +You can assign the resource filter created, in combination with roles, to a [user](../../../user-management/new-user.md#create-a-new-user) to enforce access restriction. Palette provisions two types of roles: -* [Palette Global Roles](../../..//user-management/palette-rbac/resource-scope-roles-permissions.md#paletteglobalresourceroles), the set of roles that are available in Palette console +* [Palette Global Roles](../../..//user-management/palette-rbac/resource-scope-roles-permissions.md#palette-global-resource-roles), the set of roles that are available in Palette by default. -* [Custom Resource Roles](../../..//user-management/palette-rbac/resource-scope-roles-permissions.md#palettecustomresourceroles), can be generated according to your requirements from the available set of permissions and operations. +* [Custom Resource Roles](../../..//user-management/palette-rbac/resource-scope-roles-permissions.md#palette-custom-resource-roles), can be generated according to your requirements from the available set of permissions and operations. ### Prerequisites * A [Palette account](https://console.spectrocloud.com) with Tenant scope privileges. -* A [user created](../../../user-management/new-user.md#createanewuser) to assign the resource privileges. +* A [user created](../../../user-management/new-user.md#create-a-new-user) to assign the resource privileges. To assign the resource roles and filter to the user follow the below steps:
@@ -104,5 +104,5 @@ Upon creating a filter, a display message will pop up to confirm the successful ## Resource -* [Create a New User](../../..//user-management/new-user.md#createanewuser) +* [Create a New User](../../..//user-management/new-user.md#create-a-new-user) diff --git a/docs/docs-content/clusters/cluster-management/monitoring/deploy-agent.md b/docs/docs-content/clusters/cluster-management/monitoring/deploy-agent.md index a5c68860d1..edeb071e85 100644 --- a/docs/docs-content/clusters/cluster-management/monitoring/deploy-agent.md +++ b/docs/docs-content/clusters/cluster-management/monitoring/deploy-agent.md @@ -177,7 +177,7 @@ Example: `https://metrics.example.com:9090/api/v1/write` - url: "https://metrics.example.com:9090/api/v1/write" ``` -8. Add the `basic_auth` parameters shown below. Replace `` and `` with the actual credential values. Use the username you created to authenticate with the Prometheus API server. If you followed the [Deploy a Monitoring Stack](deploy-monitor-stack.md#deployamonitoringstack) with authentication guide, then the username is `agent`. +8. Add the `basic_auth` parameters shown below. Replace `` and `` with the actual credential values. Use the username you created to authenticate with the Prometheus API server. If you followed the [Deploy a Monitoring Stack](deploy-monitor-stack.md#deploy-a-monitoring-stack) with authentication guide, then the username is `agent`.
diff --git a/docs/docs-content/clusters/cluster-management/palette-webctl.md b/docs/docs-content/clusters/cluster-management/palette-webctl.md index f2ae782ef4..b3a1f33f89 100644 --- a/docs/docs-content/clusters/cluster-management/palette-webctl.md +++ b/docs/docs-content/clusters/cluster-management/palette-webctl.md @@ -32,7 +32,7 @@ If you are using Palette Virtual Machine (VM) Management, you can find steps on :::warning -If you are using [OIDC](/clusters/cluster-management/cluster-rbac#userbacwithoidc) with your host cluster, you will need the kubelogin plugin. Refer to the kubelogin GitHub repository [README](https://github.com/int128/kubelogin#setup) for installation guidance. +If you are using [OIDC](./cluster-rbac.md) with your host cluster, you will need the kubelogin plugin. Refer to the kubelogin GitHub repository [README](https://github.com/int128/kubelogin#setup) for installation guidance. ::: diff --git a/docs/docs-content/clusters/edge/site-deployment/deploy-cluster.md b/docs/docs-content/clusters/edge/site-deployment/deploy-cluster.md index 9b6e37073c..a30dd29c86 100644 --- a/docs/docs-content/clusters/edge/site-deployment/deploy-cluster.md +++ b/docs/docs-content/clusters/edge/site-deployment/deploy-cluster.md @@ -438,7 +438,7 @@ The next step is to use the following `docker run` command to trigger Packer bui - The `cd /edge/vmware/packer/ && packer build -force --var-file=vsphere.hcl build.pkr.hcl` shell sub-command changes to the container's **/edge/vmware/packer/** directory and invokes `packer build` to create the VM template. The `packer build` command has the following options: - The `-force` flag destroys any existing template. - - The `--var-file` option reads the **vsphere.hcl** file from the container. This file contains the VM template name, VM configuration, and ISO file name to use. The VM configuration conforms to the [minimum device requirements](../architecture/#minimum-device-requirements). + - The `--var-file` option reads the **vsphere.hcl** file from the container. This file contains the VM template name, VM configuration, and ISO file name to use. The VM configuration conforms to the [minimum device requirements](../architecture.md#minimum-device-requirements). The **vsphere.hcl** file content is shown below for your reference. This tutorial does not require you to modify these configurations. diff --git a/docs/docs-content/clusters/public-cloud/aws/aws.md b/docs/docs-content/clusters/public-cloud/aws/aws.md index 4094e3fa46..c7e162aca0 100644 --- a/docs/docs-content/clusters/public-cloud/aws/aws.md +++ b/docs/docs-content/clusters/public-cloud/aws/aws.md @@ -7,7 +7,7 @@ hide_table_of_contents: false --- -Palette supports integration with [Amazon Web Services](https://aws.amazon.com). You can deploy and manage [Host Clusters](../../../glossary-all.md#hostcluster) in AWS. To get started check out the [Register and Manage AWS Accounts](add-aws-accounts.md). +Palette supports integration with [Amazon Web Services](https://aws.amazon.com). You can deploy and manage [Host Clusters](../../../glossary-all.md#host-cluster) in AWS. To get started check out the [Register and Manage AWS Accounts](add-aws-accounts.md). diff --git a/docs/docs-content/clusters/public-cloud/azure/azure.md b/docs/docs-content/clusters/public-cloud/azure/azure.md index cf539c46c0..f2887d08a5 100644 --- a/docs/docs-content/clusters/public-cloud/azure/azure.md +++ b/docs/docs-content/clusters/public-cloud/azure/azure.md @@ -8,7 +8,7 @@ tags: - azure --- -Palette supports integration with [Microsoft Azure](https://azure.microsoft.com/en-us). You can deploy and manage [Host Clusters](../../../glossary-all.md#hostcluster) in Azure or Azure Government. To get started check out the [Register and Manage Azure Cloud Account](azure-cloud.md#manage-azure-accounts). +Palette supports integration with [Microsoft Azure](https://azure.microsoft.com/en-us). You can deploy and manage [Host Clusters](../../../glossary-all.md#host-cluster) in Azure or Azure Government. To get started check out the [Register and Manage Azure Cloud Account](azure-cloud.md). @@ -23,7 +23,10 @@ To learn more about Palette and Azure cluster creation and its capabilities chec - [Register and Manage Azure Cloud Account](azure-cloud.md) -- [Create and Manage Azure Cluster](create-azure-cluster.md#deploy-an-azure-cluster-with-palette) +- [Create and Manage IaaS Azure Cluster](create-azure-cluster.md) + + +- [Create and Manage Azure AKS Cluster](aks.md) - [Deleting an Azure Cluster](../../cluster-management/remove-clusters.md) diff --git a/docs/docs-content/clusters/public-cloud/azure/create-azure-cluster.md b/docs/docs-content/clusters/public-cloud/azure/create-azure-cluster.md index 875226b6c9..56d9569585 100644 --- a/docs/docs-content/clusters/public-cloud/azure/create-azure-cluster.md +++ b/docs/docs-content/clusters/public-cloud/azure/create-azure-cluster.md @@ -86,7 +86,7 @@ Use the following steps to deploy an Azure cluster. :::warning - If the Azure account is registered with **Disable Properties** and **Static Placement** options enabled, then Palette will not import the network information from your Azure account. You can manually input the information for the **Control Plane Subnet** and the **Worker Network**, but be aware that **drop-down Menu** selections will be empty. To learn more about these settings and certain requirements to use them, refer to [Disable Properties](azure-cloud.md#disable-properties). + If the Azure account is registered with **Disable Properties** and **Static Placement** options enabled, then Palette will not import the network information from your Azure account. You can manually input the information for the **Control Plane Subnet** and the **Worker Network**, but be aware that **drop-down Menu** selections will be empty. To learn more about these settings and certain requirements to use them, refer to [Disable Properties](azure-cloud.md#disable-palette-network-calls-to-azure-account). ::: diff --git a/docs/docs-content/clusters/public-cloud/deploy-k8s-cluster.md b/docs/docs-content/clusters/public-cloud/deploy-k8s-cluster.md index 5ae8a1af78..73db36173a 100644 --- a/docs/docs-content/clusters/public-cloud/deploy-k8s-cluster.md +++ b/docs/docs-content/clusters/public-cloud/deploy-k8s-cluster.md @@ -1243,7 +1243,7 @@ In this tutorial, you created a cluster profile, which is a template that contai Palette assures consistency across cluster deployments through cluster profiles. Palette also enables you to quickly deploy applications to a Kubernetes environment with little or no prior Kubernetes knowledge. In a matter of minutes, you were able to provision a new Kubernetes cluster and deploy an application. -We encourage you to check out the [Deploy an Application using Palette Dev Engine](/devx/apps/deploy-app) tutorial to learn more about Palette. Palette Dev Engine can help you deploy applications more quickly through the usage of [virtual clusters](/glossary-all#palettevirtualcluster). Feel free to check out the reference links below to learn more about Palette. +We encourage you to check out the [Deploy an Application using Palette Dev Engine](/devx/apps/deploy-app) tutorial to learn more about Palette. Palette Dev Engine can help you deploy applications more quickly through the usage of [virtual clusters](../../glossary-all.md#palette-virtual-cluster). Feel free to check out the reference links below to learn more about Palette.
diff --git a/docs/docs-content/compliance.md b/docs/docs-content/compliance.md deleted file mode 100644 index 922debd194..0000000000 --- a/docs/docs-content/compliance.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -sidebar_label: "Compliance" -title: "Certification of Compliance" -description: "Certification of Compliance" -hide_table_of_contents: false -sidebar_position: 220 -sidebar_custom_props: - icon: "user-shield" -tags: ["compliance", "soc2", "fips"] ---- - -We have two Security Operations Center (SOC) certifications and a FIPS certificate for a Cryptographic Module. - -## SOC 2 Type II - -![soc2.png](/soc2.png "#width=180px") - -Spectro Cloud is certified against SOC2 Type II, compliance with the AICPA’s (American Institute of Certified Public Accountants) TSC (Trust Services Criteria). -* Spectro Cloud SOC 2 Type II audit report assures our organization’s: - * Security - * Availability - * Processing integrity - * Confidentiality - * Privacy -* SOC 2 audits are an important component in regulatory oversight, vendor management programs, internal governance, and risk management. -* These reports help the users and their auditors to understand the Spectro Cloud controls established to support operations and compliance. -* The annual certification of SOC2 is Independent 3rd Party Auditor. -* Spectro Cloud SOC 2 Type II report is available upon request for any customers or prospects with signed MNDA. - -## FIPS 140-2 - - -![FIPS-Compliance](/docs_compliance_compliance_fips-logo.png "#width=180px") - -Spectro Cloud is certified against FIPS 140-2 with [Certificate number 4349](https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4349) in compliance with the Cryptographic Module Validation Program (CMVP). - -Our Spectro Cloud Cryptographic Module is a general-purpose cryptographic library. The FIPS-enforced Palette VerteX edition incorporates the module in the Kubernetes Management Platform and the infrastructure components of target clusters to protect the sensitive information of regulated industries. Palette VerteX supports FIPS at the tenant level. For more information about the FIPS-enforced Palette edition, check out [Palette VerteX](vertex/vertex.md). - -The module is tested against these configurations: - -* Red Hat Enterprise Linux 8 on Dell PowerEdge R440 with Intel Xeon Silver 4214R _with and without_ PAA -* SUSE Linux Enterprise Server 15 on Dell PowerEdge R450 with Intel Xeon Silver 4309Y _with and without_ PAA -* Ubuntu 18.04 on Dell PowerEdge R450 with Intel Xeon Silver 4309Y _with and without_ PAA -* Ubuntu 20.04 on Dell PowerEdge R450 with Intel Xeon Silver 4309Y _with and without_ PAA diff --git a/docs/docs-content/devx/devx.md b/docs/docs-content/devx/devx.md index 91a4d22d14..786aad5c37 100644 --- a/docs/docs-content/devx/devx.md +++ b/docs/docs-content/devx/devx.md @@ -61,7 +61,7 @@ The PDE dashboard provides a snapshot of resource utilization in your PDE enviro ## Automation Support -You can manage PDE resources through the [Palette API](/api/introduction), [Spectro Cloud Terraform provider](https://registry.terraform.io/providers/spectrocloud/spectrocloud/latest/docs), and the Palette CLI. Download the Palette CLI from the [Downloads](/spectro-downloads#palettecli) page to start programmatically using PDE. +You can manage PDE resources through the [Palette API](/api/introduction), [Spectro Cloud Terraform provider](https://registry.terraform.io/providers/spectrocloud/spectrocloud/latest/docs), and the Palette CLI. Download the Palette CLI from the [Downloads](../spectro-downloads.md#palette-cli) page to start programmatically using PDE. ![A view of the Palette CLI menu from a terminal](/devx_devx_cli-display.png) diff --git a/docs/docs-content/devx/services/service-listings/vault.md b/docs/docs-content/devx/services/service-listings/vault.md index 7ac5671913..2e70faddb2 100644 --- a/docs/docs-content/devx/services/service-listings/vault.md +++ b/docs/docs-content/devx/services/service-listings/vault.md @@ -140,7 +140,7 @@ You can validate the Vault instance deployed successfully by using the following 10. Open your browser and visit [https://localhost:8200/ui](https://localhost:8200/ui) to access the Vault UI. You will receive a warning due to the usage of a self-signed certificate but you can ignore this warning. -To acquire the Vault root token, review the [Vault Credentials](vault.md#vault-credentials) section. +To acquire the Vault root token, review the [Vault Credentials](#vault-credentials) section. # Output Variables diff --git a/docs/docs-content/enterprise-version/install-palette/airgap/vmware-vsphere-airgap-instructions.md b/docs/docs-content/enterprise-version/install-palette/airgap/vmware-vsphere-airgap-instructions.md index 91fb9e4803..bae9fbc3ac 100644 --- a/docs/docs-content/enterprise-version/install-palette/airgap/vmware-vsphere-airgap-instructions.md +++ b/docs/docs-content/enterprise-version/install-palette/airgap/vmware-vsphere-airgap-instructions.md @@ -76,7 +76,7 @@ Carefully review the [prerequisites](#prerequisites) section before proceeding. - Palette CLI installed and available. Refer to the Palette CLI [Install](../../../palette-cli/install-palette-cli.md#download-and-setup) page for guidance. -- Review the required vSphere [permissions](../install-on-vmware/vmware-system-requirements.md). Ensure you have created the proper custom roles and zone tags. Zone tagging is required for dynamic storage allocation across fault domains when provisioning workloads that require persistent storage. Refer to [Zone Tagging](../install-on-vmware/install-on-vmware.md#vsphere-machine-configuration) for information. +- Review the required vSphere [permissions](../install-on-vmware/vmware-system-requirements.md). Ensure you have created the proper custom roles and zone tags. Zone tagging is required for dynamic storage allocation across fault domains when provisioning workloads that require persistent storage. Refer to [Zone Tagging](../install-on-vmware/vmware-system-requirements.md) for information.
diff --git a/docs/docs-content/enterprise-version/install-palette/install-on-vmware/install.md b/docs/docs-content/enterprise-version/install-palette/install-on-vmware/install.md index bdef523ae9..b38ce9de29 100644 --- a/docs/docs-content/enterprise-version/install-palette/install-on-vmware/install.md +++ b/docs/docs-content/enterprise-version/install-palette/install-on-vmware/install.md @@ -65,7 +65,7 @@ If you are installing Palette in an airgap environment, ensure you complete all - x509 SSL certificate authority file in base64 format. This file is optional. -- Zone tagging is required for dynamic storage allocation across fault domains when provisioning workloads that require persistent storage. Refer to [Zone Tagging](../install-on-vmware/install-on-vmware.md#vsphere-machine-configuration) for information. +- Zone tagging is required for dynamic storage allocation across fault domains when provisioning workloads that require persistent storage. Refer to [Zone Tagging](../install-on-vmware/vmware-system-requirements.md) for information. - Assigned IP addresses for application workload services, such as Load Balancer services. diff --git a/docs/docs-content/integrations/kubernetes-edge.md b/docs/docs-content/integrations/kubernetes-edge.md index 82514ca8c2..41b384876d 100644 --- a/docs/docs-content/integrations/kubernetes-edge.md +++ b/docs/docs-content/integrations/kubernetes-edge.md @@ -41,7 +41,7 @@ We also offer Palette eXtended Kubernetes (PXK) for cloud and data center deploy ### PXK and Palette VerteX -The PXK-E used in [Palette VerteX](../vertex/vertex.md) is compiled and linked with our [NIST-certified FIPS crypto module](../compliance.md#fips-140-2). PXK-E is by default enabled with [Ubuntu Pro](https://ubuntu.com/pro) with FIPS mode enabled. Additionally, the Operating System (OS) is hardened based on the NIST-800 standard. Refer to the [Build Edge Artifacts](../clusters/edge/edgeforge-workflow/build-artifacts.md) guide to learn more on how to build the PXK-E image with FIPS mode enabled. +The PXK-E used in [Palette VerteX](../vertex/vertex.md) is compiled and linked with our [NIST-certified FIPS crypto module](../legal-licenses/compliance.md#fips-140-2). PXK-E is by default enabled with [Ubuntu Pro](https://ubuntu.com/pro) with FIPS mode enabled. Additionally, the Operating System (OS) is hardened based on the NIST-800 standard. Refer to the [Build Edge Artifacts](../clusters/edge/edgeforge-workflow/build-artifacts.md) guide to learn more on how to build the PXK-E image with FIPS mode enabled. The combined usage of PXK-E and Palette VerteX provides a secure and FIPS-compliant experience as the Kubernetes distribution, OS, and management platform VerteX is FIPS-compliant. diff --git a/docs/docs-content/integrations/kubernetes.md b/docs/docs-content/integrations/kubernetes.md index 218e8b67dc..c68d007fc9 100644 --- a/docs/docs-content/integrations/kubernetes.md +++ b/docs/docs-content/integrations/kubernetes.md @@ -36,7 +36,7 @@ We also offer Palette eXtended Kubernetes Edge (PXK-E) for Edge deployments. Ref ### PXK and Palette VerteX -The PXK used in [Palette VerteX](../vertex/vertex.md) is compiled and linked with our [NIST-certified FIPS crypto module](../compliance.md#fips-140-2). PXK is by default enabled with [Ubuntu Pro](https://ubuntu.com/pro) with FIPS mode enabled. Additionally, the Operating System (OS) is hardened based on the NIST-800 standard. However, if you use a different OS through the [BYOOS](./byoos.md) pack, then you are responsible for ensuring FIPS compliance and hardening of the OS. +The PXK used in [Palette VerteX](../vertex/vertex.md) is compiled and linked with our [NIST-certified FIPS crypto module](../legal-licenses/compliance.md#fips-140-2) PXK is by default enabled with [Ubuntu Pro](https://ubuntu.com/pro) with FIPS mode enabled. Additionally, the Operating System (OS) is hardened based on the NIST-800 standard. However, if you use a different OS through the [BYOOS](./byoos.md) pack, then you are responsible for ensuring FIPS compliance and hardening of the OS. The combined usage of PXK and Palette VerteX provides a secure and FIPS-compliant experience as the Kubernetes distribution, OS, and management platform VerteX is FIPS-compliant. diff --git a/docs/docs-content/integrations/ubuntu.md b/docs/docs-content/integrations/ubuntu.md index 514f162c69..ceafe9bfc7 100644 --- a/docs/docs-content/integrations/ubuntu.md +++ b/docs/docs-content/integrations/ubuntu.md @@ -74,7 +74,7 @@ Palette applies a default set of configuration options when deploying Ubuntu. Yo | `controllerManager` | Extra settings for the Kubernetes controller manager control plane component. Review the [Kubernetes controller manager](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/) documentation for more information. | object | No | | `scheduler` | Extra settings for the Kubernetes scheduler control plane component. Refer to the [Kube scheduler](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler) documenation for more details. | object | No | | `kubeletExtraArgs` | Extra arguments for kubelet. Refer to the [Kubeadm init](https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init) documentation for more details. | map | No | -| `files` | Create or specify additional files for the `kubeadmconfig`. Refer to the [Customize Pack](/integrations/ubuntu?22.04.x#customizepack) section to learn more. | list | No | +| `files` | Create or specify additional files for the `kubeadmconfig`. Refer to the [Customize Pack](#customize-pack) section to learn more. | list | No | | `preKubeadmCommands` | Extra commands to issue before kubeadm starts. | list | No | | `postKubeadmCommands` | Extra commands to issue after kubeadm starts. | list | No | | `imageRepository` | The container registry to pull images from. If empty, `k8s.gcr.io` will be used by default. | string | No | @@ -178,7 +178,7 @@ Review the parameter documentation before you make changes to the kubeadm config ::: -Palette also supports Ubuntu Pro. Refer to the [Ubuntu Pro](ubuntu.md?22.04.x#ubuntupro) section below for more details. +Palette also supports Ubuntu Pro. Refer to the [Ubuntu Pro](#ubuntu-pro) section below for more details.
@@ -415,7 +415,7 @@ Palette applies a default set of configuration options when deploying Ubuntu. Yo | `controllerManager` | Extra settings for the Kubernetes controller manager control plane component. Review the [Kubernetes controller manager](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/) documentation for more information. | object | No | | `scheduler` | Extra settings for the Kubernetes scheduler control plane component. Refer to the [Kube scheduler](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler) documenation for more details. | object | No | | `kubeletExtraArgs` | Extra arguments for kubelet. Refer to the [Kubeadm init](https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init) documentation for more details. | map | No | -| `files` | Additional files to pass to kubeadmconfig. Refer to the [Customize Pack](/integrations/ubuntu?22.04.x#customizepack) section to learn more. | list | No | +| `files` | Additional files to pass to kubeadmconfig. Refer to the [Customize Pack](#add-custom-files-1) section to learn more. | list | No | | `preKubeadmCommands` | Extra commands to issue before kubeadm starts. | list | Yes - Auto generated | | `postKubeadmCommands` | Extra commands to issue after kubeadm starts. | list | Yes - Auto generated | | `imageRepository` | The container registry to pull images from. If empty, `k8s.gcr.io` will be used by default. | string | No | @@ -519,7 +519,7 @@ Review the parameter documentation before you make changes to the kubeadm config ::: -Palette also supports Ubuntu Pro. Refer to the [Ubuntu Pro](ubuntu.md?22.04.x#ubuntupro) section below for more details. +Palette also supports Ubuntu Pro. Refer to the [Ubuntu Pro](#ubuntu-pro-1) section below for more details.
diff --git a/docs/docs-content/introduction/introduction.md b/docs/docs-content/introduction/introduction.md index 0164a09562..b3321cce1b 100644 --- a/docs/docs-content/introduction/introduction.md +++ b/docs/docs-content/introduction/introduction.md @@ -54,7 +54,7 @@ Development teams will get the flexibility and freedom they are looking for to i ### IT Operations and SREs -Declarative management makes life easier for IT teams, with consistency, repeatability, and all the enterprise-grade controls and governance they need - especially when moving to production [Cluster Profiles](/glossary-all#clusterprofile) enable them to define and re-use full-stack clusters and support them across the entire lifecycle without having to write scripts, as well as integrate with existing tools and methodologies. +Declarative management makes life easier for IT teams, with consistency, repeatability, and all the enterprise-grade controls and governance they need - especially when moving to production [Cluster Profiles](../profiles/cluster-profiles/cluster-profiles.md) enable them to define and re-use full-stack clusters and support them across the entire lifecycle without having to write scripts, as well as integrate with existing tools and methodologies. ### IT Executives diff --git a/docs/docs-content/legal-licenses/compliance.md b/docs/docs-content/legal-licenses/compliance.md new file mode 100644 index 0000000000..db38dbc682 --- /dev/null +++ b/docs/docs-content/legal-licenses/compliance.md @@ -0,0 +1,57 @@ +--- +sidebar_label: "Compliance" +title: "Certification of Compliance" +description: "Certification of Compliance" +hide_table_of_contents: false +sidebar_position: 10 +tags: ["compliance", "soc2", "fips"] +--- + + + +## ISO 27001 + +![ISO 27001 logo](/legal-licenses_compliance_iso-27001.png "#width=300px") + +The International Organization for Standardization 27001 Standard (ISO 27001) is one of the leading international standards focused on information security. Spectro Cloud has obtained the ISO 27001 Certification and undergoes periodic audits to maintain this certification. ISO 27001 Certification provides assurances that Spectro Cloud is identifying and managing risks effectively, consistently, and measurably. + + +Below are some reasons why an ISO 27001 Certification is important: + +- Customer trust and confidence: Clients and partners often look for assurances that their sensitive information is handled securely. Achieving ISO 27001 certification can enhance customer trust and confidence, potentially leading to increased business opportunities. + +- Risk Management: By implementing ISO controls and measures, companies can mitigate these risks, protecting sensitive data from unauthorized access or disclosure. + +- Legal and regulatory compliance: Adhering to ISO 27001 demonstrates a commitment to information security, which can help organizations comply with various legal and regulatory requirements related to data protection and privacy. + +- Global recognition: ISO 27001 is globally recognized. This helps organizations communicate their commitment to information security across borders. + + +## SOC 2 Type II + +![soc2.png](/soc2.png "#width=180px") + +The American Institute of Certified Public Accountants (AICPA) Service Organization Controls (SOC) Attestation provides assurances over control environments. Spectro Cloud’s SOC 2 Type II audit report provides assurances of our organization’s security and availability. + +- SOC 2 audits are an important component in regulatory oversight, vendor management programs, internal governance, and risk management. + +- These reports help our users and their auditors understand the controls established at Spectro Cloud to support operations and compliance. + +- Spectro Cloud’s SOC 2 Type II report is available upon request for any customers or prospects with a signed non-disclosure agreement in place. + + +## FIPS 140-2 + + +![FIPS-Compliance](/docs_compliance_compliance_fips-logo.png "#width=180px") + +Spectro Cloud is validated against FIPS 140-2 with [Certificate number 4349](https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4349) in compliance with the Cryptographic Module Validation Program (CMVP). + +Our Spectro Cloud Cryptographic Module is a general-purpose cryptographic library. The FIPS-enforced Palette VerteX edition incorporates the module in the Kubernetes Management Platform and the infrastructure components of target clusters to protect the sensitive information of regulated industries. Palette VerteX supports FIPS at the tenant level. For more information about the FIPS-enforced Palette edition, check out [Palette VerteX](vertex/vertex.md). + +The module is tested against these configurations: + +* Red Hat Enterprise Linux 8 on Dell PowerEdge R440 with Intel Xeon Silver 4214R _with and without_ PAA +* SUSE Linux Enterprise Server 15 on Dell PowerEdge R450 with Intel Xeon Silver 4309Y _with and without_ PAA +* Ubuntu 18.04 on Dell PowerEdge R450 with Intel Xeon Silver 4309Y _with and without_ PAA +* Ubuntu 20.04 on Dell PowerEdge R450 with Intel Xeon Silver 4309Y _with and without_ PAA diff --git a/docs/docs-content/legal-licenses/legal-licenses.md b/docs/docs-content/legal-licenses/legal-licenses.md index 61c029fde1..37e4f55106 100644 --- a/docs/docs-content/legal-licenses/legal-licenses.md +++ b/docs/docs-content/legal-licenses/legal-licenses.md @@ -1,8 +1,8 @@ --- -sidebar_label: "Legal & Acknowledgments" -title: "Legal & Acknowledgments" -description: "Review the legal and open source components used in Palette." -sidebar_position: 10 +sidebar_label: "Compliance & Legal" +title: "Compliance & Legal" +description: "Review legal, compliance, and open source components used in Palette." +sidebar_position: 0 hide_table_of_contents: false sidebar_custom_props: icon: "gavel" @@ -16,6 +16,7 @@ This section contains legal information and acknowledgments for Palette and Pale ## Resources - [About Us](https://www.spectrocloud.com/company) +- [Compliance](compliance.md) - [Open-Source Licenses](oss-licenses.md) - [Partners](https://www.spectrocloud.com/partners) - [Security Bulletins](../security/security-bulletins/security-bulletins.md) \ No newline at end of file diff --git a/docs/docs-content/legal-licenses/oss-licenses.md b/docs/docs-content/legal-licenses/oss-licenses.md index 911de1027b..ea943f08be 100644 --- a/docs/docs-content/legal-licenses/oss-licenses.md +++ b/docs/docs-content/legal-licenses/oss-licenses.md @@ -2,7 +2,7 @@ sidebar_label: "Open-source Licenses" title: "Open-source Licenses" description: "Review the open-source licenses tied to the libraries and modules currently in use by Palette." -sidebar_position: 10 +sidebar_position: 30 tags: ["legal", "licenses"] --- diff --git a/docs/docs-content/profiles/app-profiles/app-profile-output-vars.md b/docs/docs-content/profiles/app-profiles/app-profile-output-vars.md index 32228a6126..ae6c8b3fae 100644 --- a/docs/docs-content/profiles/app-profiles/app-profile-output-vars.md +++ b/docs/docs-content/profiles/app-profiles/app-profile-output-vars.md @@ -8,7 +8,7 @@ tags: ["devx", "app mode", "pde", "app profiles"] --- -Palette Dev Engine output variables are defined in the [app profile](/glossary-all#appprofile) and are only resolved at cluster deployment time. The output variables have the following properties: +Palette Dev Engine output variables are defined in the [app profile](../../glossary-all.md#app-profile) and are only resolved at cluster deployment time. The output variables have the following properties: * May be referenced by specifying them during app profile creation. @@ -75,7 +75,7 @@ Each database service exposes a set of output variables. To learn about each dat ## Resources -* [Palette System Macros](/registries-and-packs/pack-constraints#packmacros) +* [Palette System Macros](../../registries-and-packs/pack-constraints.md#pack-macros) -* [Palette User Macros](/clusters/cluster-management/macros#overview) +* [Palette User Macros](../../clusters/cluster-management/macros.md)
diff --git a/docs/docs-content/registries-and-packs/deploy-pack.md b/docs/docs-content/registries-and-packs/deploy-pack.md index 22350b2405..4472913032 100644 --- a/docs/docs-content/registries-and-packs/deploy-pack.md +++ b/docs/docs-content/registries-and-packs/deploy-pack.md @@ -920,7 +920,7 @@ cd /terraform/pack-tf ### Set Up the Spectro Cloud API Key -To get started with Terraform code, you need a Palette API key to authenticate and interact with the Palette API endpoint. To add a new API key, log in to Palette, click on the **User Menu** at the top right, and select **My API Keys**, as shown in the screenshot below. Visit the [Create API Key](https://docs.spectrocloud.com/user-management/authentication/api-key/create-api-key/) guide for more information. +To get started with Terraform code, you need a Palette API key to authenticate and interact with the Palette API endpoint. To add a new API key, log in to Palette, click on the **User Menu** at the top right, and select **My API Keys**, as shown in the screenshot below. Visit the [Create API Key](../user-management/authentication/api-key/create-api-key.md) guide for more information. ![Screenshot of generating an API key in Palette.](/tutorials/deploy-pack/registries-and-packs_deploy-pack_generate-api-key.png) @@ -1260,7 +1260,7 @@ Packs are the building blocks of cluster profiles, allowing you to customize you To learn more about packs in Palette, we encourage you to check out the reference resources below. -- [Custom OS Pack](add-custom-packs.md#add-a-custom-pack) +- [Custom OS Pack](../integrations/byoos.md) - [Add-on Packs](adding-add-on-packs.md) diff --git a/docs/docs-content/security/security.md b/docs/docs-content/security/security.md index 7b2fa45aee..ef8c81f4ae 100644 --- a/docs/docs-content/security/security.md +++ b/docs/docs-content/security/security.md @@ -28,7 +28,7 @@ Palette uses a micro services-based architecture, and we take steps to ensure ea ## Compliance & Standards -We believe adherence to industry standards and regulations is critical to maintaining the highest levels of security for our customers. We ensure our software complies with all relevant laws and regulations, and we continuously evaluate and update our compliance efforts to stay current with emerging regulations and requirements. To learn about our product certifications, check out the [Compliance](/compliance) reference. +We believe adherence to industry standards and regulations is critical to maintaining the highest levels of security for our customers. We ensure our software complies with all relevant laws and regulations, and we continuously evaluate and update our compliance efforts to stay current with emerging regulations and requirements. To learn about our product certifications, check out the [Compliance](../legal-licenses/compliance.md) reference.
diff --git a/docs/docs-content/troubleshooting/cluster-deployment.md b/docs/docs-content/troubleshooting/cluster-deployment.md index ed9882a8c5..18c7884013 100644 --- a/docs/docs-content/troubleshooting/cluster-deployment.md +++ b/docs/docs-content/troubleshooting/cluster-deployment.md @@ -126,7 +126,7 @@ We recommend only applying the labels to namespaces where pods fail to be create If your pack creates multiple namespaces, and you are unsure which ones contain pods that need the elevated privileges, you can access the cluster with the kubectl CLI and use the `kubectl get pods` command. This command lists pods and their namespaces so you can identify the pods that are failing at creation. -For guidance in using the CLI, review [Access Cluster with CLI](../clusters/cluster-management/palette-webctl/#access-cluster-with-cli). To learn more about kubectl pod commands, refer to the [Kubernetes](https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#get) documentation. +For guidance in using the CLI, review [Access Cluster with CLI](../clusters/cluster-management/palette-webctl.md#access-cluster-with-cli). To learn more about kubectl pod commands, refer to the [Kubernetes](https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#get) documentation. ::: diff --git a/docs/docs-content/user-management/palette-rbac/palette-rbac.md b/docs/docs-content/user-management/palette-rbac/palette-rbac.md index 604650507f..bf3eff5dcd 100644 --- a/docs/docs-content/user-management/palette-rbac/palette-rbac.md +++ b/docs/docs-content/user-management/palette-rbac/palette-rbac.md @@ -109,7 +109,7 @@ Tenant is an isolated workspace within the Palette. `Users` and `Teams` with spe ### Project -The Global Project Scope holds a group of resources, in a logical grouping, to a specific project. The project acts as a namespace for resource management. Users and Teams with specific roles can be associated with the project, cluster, or cluster profile you create. Users are members of a tenant who are assigned [project scope roles](project-scope-roles-permissions.md#global-project-scope) that control their access within the platform. +The Global Project Scope holds a group of resources, in a logical grouping, to a specific project. The project acts as a namespace for resource management. Users and Teams with specific roles can be associated with the project, cluster, or cluster profile you create. Users are members of a tenant who are assigned [project scope roles](./project-scope-roles-permissions.md) that control their access within the platform.
## Palette Specific (Default) Roles: @@ -203,7 +203,7 @@ The Default (built-in) roles of Palette can be directly assigned to a user. The 1. Login to Palette console as `Tenant Admin`. -2. Select **Users and Teams** from the left **Main Menu** to list the [created users](../user-management.md#user-management). +2. Select **Users and Teams** from the left **Main Menu** to list the created users. 3. From the list of users **select the user** to be assigned with role to open the role addition wizard. @@ -261,7 +261,7 @@ Palette enables the users to have custom Roles. These custom roles can be create To create a custom role, login to the Palette console as `Tenant Admin`: -1. Go to **Roles** from the left ribbon menu +1.From the left **Main Menu**, click on **Tenant Settings** and select **Roles**. 2. Click **Create Role**, to open the `Add New Role` wizard @@ -292,7 +292,7 @@ To create a custom role, login to the Palette console as `Tenant Admin`: **Example:** -If the user is creating a role under the Tenant scope for API Key operations, select the `API Key Permissions` and then from the drop-down menu of that permission, check (tick) the required API operations listed under API Key permissions. Similarly, several permissions can be combined to create a **Custom Role**. [The created role can be assigned to an existing or new user.](/user-management#rolesandpermissions) +If the user is creating a role under the Tenant scope for API Key operations, select the `API Key Permissions` and then from the drop-down menu of that permission, check (tick) the required API operations listed under API Key permissions. Similarly, several permissions can be combined to create a **Custom Role**. The created role can be assigned to an existing or new user.

@@ -302,7 +302,7 @@ If the user is creating a role under the Tenant scope for API Key operations, se 1. Login to Palette console as `Tenant Admin`. -2. Select **Users and Teams** from the left ribbon menu to list the [created users](../user-management.md#user-management). +2. Select **Users and Teams** from the left ribbon menu to list the [created users](../user-management.md). 3. From the list of users **select the user** to be assigned with role to open the role addition wizard. diff --git a/docs/docs-content/user-management/user-management.md b/docs/docs-content/user-management/user-management.md index 61070ee354..6be6bcde1d 100644 --- a/docs/docs-content/user-management/user-management.md +++ b/docs/docs-content/user-management/user-management.md @@ -9,10 +9,6 @@ tags: ["user-management"] --- - - -# User Management - This section touches upon the initial login aspects for Tenant Admins and non-admin users and the RBAC setup within Palette. ## User Login diff --git a/docs/docs-content/vertex/install-palette-vertex/airgap/vmware-vsphere-airgap-instructions.md b/docs/docs-content/vertex/install-palette-vertex/airgap/vmware-vsphere-airgap-instructions.md index 3f6d8c965c..fbe5e219d3 100644 --- a/docs/docs-content/vertex/install-palette-vertex/airgap/vmware-vsphere-airgap-instructions.md +++ b/docs/docs-content/vertex/install-palette-vertex/airgap/vmware-vsphere-airgap-instructions.md @@ -76,7 +76,7 @@ Carefully review the [prerequisites](#prerequisites) section before proceeding. - Palette CLI installed and available. Refer to the Palette CLI [Install](../../../palette-cli/install-palette-cli.md#download-and-setup) page for guidance. -- Review the required vSphere [permissions](../install-on-vmware/vmware-system-requirements.md). Ensure you have created the proper custom roles and zone tags. Zone tagging is required for dynamic storage allocation across fault domains when provisioning workloads that require persistent storage. Refer to [Zone Tagging](../install-on-vmware/install-on-vmware.md#vsphere-machine-configuration) for information. +- Review the required vSphere [permissions](../install-on-vmware/vmware-system-requirements.md). Ensure you have created the proper custom roles and zone tags. Zone tagging is required for dynamic storage allocation across fault domains when provisioning workloads that require persistent storage. Refer to [Zone Tagging](../install-on-vmware/vmware-system-requirements.md) for information.
diff --git a/docs/docs-content/vertex/install-palette-vertex/install-on-vmware/install.md b/docs/docs-content/vertex/install-palette-vertex/install-on-vmware/install.md index bd10008dfc..46e29f08a7 100644 --- a/docs/docs-content/vertex/install-palette-vertex/install-on-vmware/install.md +++ b/docs/docs-content/vertex/install-palette-vertex/install-on-vmware/install.md @@ -105,7 +105,7 @@ The video below demonstrates the installation wizard and the prompts you will en Use the following steps to install Palette VerteX. -1. Open a terminal window and invoke the Palette CLI by using the `ec` command to install the enterprise cluster. The interactive CLI prompts you for configuration details and then initiates the installation. For more information about the `ec` subcommand, refer to [Palette Commands](../../../palette-cli/commands/commands.md#ec). +1. Open a terminal window and invoke the Palette CLI by using the `ec` command to install the enterprise cluster. The interactive CLI prompts you for configuration details and then initiates the installation. For more information about the `ec` subcommand, refer to [Palette Commands](../../../palette-cli/commands/ec.md).
diff --git a/docs/docs-content/vertex/system-management/enable-non-fips-settings/enable-non-fips-settings.md b/docs/docs-content/vertex/system-management/enable-non-fips-settings/enable-non-fips-settings.md index 6315a57f14..19b4a16e4d 100644 --- a/docs/docs-content/vertex/system-management/enable-non-fips-settings/enable-non-fips-settings.md +++ b/docs/docs-content/vertex/system-management/enable-non-fips-settings/enable-non-fips-settings.md @@ -11,7 +11,7 @@ keywords: ["self-hosted", "vertex"] -Palette VerteX is FIPS-enforced by default, incorporating the Spectro Cloud Cryptographic Module into the Kubernetes Management Platform and the infrastructure components of target clusters. To learn more about our cryptographic library, check out [FIPS 140-2 Certification](../../../compliance.md#fips-140-2). +Palette VerteX is FIPS-enforced by default, incorporating the Spectro Cloud Cryptographic Module into the Kubernetes Management Platform and the infrastructure components of target clusters. To learn more about our cryptographic library, check out [FIPS 140-2 Certification](../../../legal-licenses/compliance.md#fips-140-2). If desired, you can allow the consumption of certain non-FIPS functionality in Palette VerteX at the tenant level. **Platform Settings** at the tenant level provide toggles to allow non-FIPS-compliant packs and non-FIPS features such as scans, backup, and restore. You can also allow importing clusters created external to Palette. @@ -27,6 +27,6 @@ If desired, you can allow the consumption of certain non-FIPS functionality in P - [Allow Cluster Import](../../system-management/enable-non-fips-settings/allow-cluster-import.md) -- [Spectro Cloud FIPS 140-2 Certification](../../../compliance.md#fips-140-2) +- [Spectro Cloud FIPS 140-2 Certification](../../../legal-licenses/compliance.md#fips-140-2) diff --git a/docs/docs-content/workspace/workload-features.md b/docs/docs-content/workspace/workload-features.md index 846691fb15..b7d48a494d 100644 --- a/docs/docs-content/workspace/workload-features.md +++ b/docs/docs-content/workspace/workload-features.md @@ -416,7 +416,7 @@ Palette enables the users to limit resource usage within the workspace optionall ## To set your Resource Quota: -1. During [Step: 3 Associate Namespaces](adding-a-new-workspace#3-associate-namespaces) of Namespace creation, **Workspace Quota** can be set by giving the **Maximum CPU** and **Maximum Memory**. Then, all the clusters launched within the Namespace can use the set Quota. +1. During [Step: 3 Associate Namespaces](./adding-a-new-workspace.md#create-your-workspace) of Namespace creation, **Workspace Quota** can be set by giving the **Maximum CPU** and **Maximum Memory**. Then, all the clusters launched within the Namespace can use the set Quota. 2. Namespace Quota can be set for an already deployed workspace as: @@ -552,7 +552,7 @@ Palette users can restrict a few container images from getting deployed into a s To restrict a container image for a particular namespace within the workspace: -1. During [Step: 4 Settings](adding-a-new-workspace.md#4-settings) of workspace creation, select the **Container Images** tab from the left ribbon. +1. During [Step: 4 Settings](adding-a-new-workspace.md#create-your-workspace) of workspace creation, select the **Container Images** tab from the left ribbon. 2. Click on **+ Add New Container Image** and provide the **Namespace** and **Restricted Images**. Multiple images can be restricted within a namespace by separating them with commas. diff --git a/docusaurus.config.js b/docusaurus.config.js index d3d76da1cf..120c8d746d 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -22,6 +22,7 @@ const config = { // Usually your repo name. onBrokenLinks: "throw", + onBrokenAnchors: "throw", onBrokenMarkdownLinks: "throw", // Even if you don't use internalization, you can use this field to set useful // metadata like html lang. For example, if your site is Chinese, you may want diff --git a/redirects.js b/redirects.js index bb970687aa..413fbb6067 100644 --- a/redirects.js +++ b/redirects.js @@ -350,6 +350,10 @@ const redirects = [ { from: `/registries-and-packs/oci-registry`, to: `/registries-and-packs/registries/oci-registry` + }, + { + from: `/compliance`, + to: `/legal-licenses/compliance` } ]; diff --git a/src/components/IconMapper/dynamicFontAwesomeImports.js b/src/components/IconMapper/dynamicFontAwesomeImports.js index e3e762977c..1a53dbda4b 100644 --- a/src/components/IconMapper/dynamicFontAwesomeImports.js +++ b/src/components/IconMapper/dynamicFontAwesomeImports.js @@ -6,7 +6,6 @@ import { faDatabase } from '@fortawesome/free-solid-svg-icons'; import { faHdd } from '@fortawesome/free-solid-svg-icons'; import { faCloudArrowDown } from '@fortawesome/free-solid-svg-icons'; import { faServer } from '@fortawesome/free-solid-svg-icons'; -import { faUserShield } from '@fortawesome/free-solid-svg-icons'; import { faUsers } from '@fortawesome/free-solid-svg-icons'; import { faWarehouse } from '@fortawesome/free-solid-svg-icons'; import { faBook } from '@fortawesome/free-solid-svg-icons'; @@ -27,7 +26,6 @@ export const fontAwesomeIcons = { "hdd": faHdd, "cloud-arrow-down": faCloudArrowDown, "server": faServer, - "user-shield": faUserShield, "users": faUsers, "warehouse": faWarehouse, "book": faBook, diff --git a/static/assets/docs/images/legal-licenses_compliance_iso-27001.png b/static/assets/docs/images/legal-licenses_compliance_iso-27001.png new file mode 100644 index 0000000000..41a0a08a27 Binary files /dev/null and b/static/assets/docs/images/legal-licenses_compliance_iso-27001.png differ