spectrocloud · karl-cardenas-coding · Jan 9, 2025 · Jan 9, 2025 · Jan 9, 2025
@@ -79,7 +79,6 @@ The following table outlines all available provider options.
 | **AWS EKS**                                    | `eks`         |
 | **GCP IaaS**                                   | `gcp`         |
 | **GCP GKE**                                    | `gke`         |
-| **TKE** (Tencent)                              | `tke`         |
 | **MAAS** (Canonical)                           | `maas`        |
 | **VMware vSphere**                             | `vsphere`     |
 | **Openstack**                                  | `openstack`   |

@@ -15,7 +15,7 @@ providers. This pack defines the default properties we use to deploy Kubernetes
 Kubernetes hardening standards that the Center for Internet Security (CIS) recommends.
 
 We also support managed Kubernetes distributions for Elastic Kubernetes Service (EKS), Azure Kubernetes Service (AKS),
-Google Kubernetes Engine (GKE), and Tencent Kubernetes Engine (TKE).
+and Google Kubernetes Engine (GKE).
 
 :::warning
 

@@ -15,7 +15,7 @@ This pack defines the default properties we use to deploy Kubernetes clusters an
 hardening standards that the Center for Internet Security (CIS) recommends.
 
 We also support managed Kubernetes distributions for Elastic Kubernetes Service (EKS), Azure Kubernetes Service (AKS),
-Google Kubernetes Engine (GKE), and Tencent Kubernetes Engine (TKE).
+and Google Kubernetes Engine (GKE).
 
 We offer PXK as a core pack in Palette.
 

@@ -29,5 +29,3 @@ The following pages provide detailed instructions for setting up new workload cl
 - [Azure](azure/azure.md)
 
 - [Google Cloud](gcp/gcp.md)
-
-- [Tencent](tke.md)
@@ -21,8 +21,8 @@ specific needs, with granular governance and enterprise-grade security.
 
 Palette has the richest coverage in supported environments that includes:
 
-- Public Clouds: AWS, Azure, Google Cloud and Tencent TKE. Palette supports both IaaS and managed Kubernetes services
-  AWS EKS, Azure AKS and Google GKE.
+- Public Clouds: AWS, Azure, and Google Cloud. Palette supports both IaaS and managed Kubernetes services AWS EKS, Azure
+  AKS, and Google GKE.
 - Data Centers: VMware, Nutanix, and OpenStack
 - Bare Metal: Canonical MAAS
 - Edge

@@ -29,7 +29,7 @@ custom image for RHEL and Konvoy.
 
 ## Terraform
 
-You can retrieve details about the Kubernetes pack for Tencent TKE by using the following Terraform code.
+You can retrieve details about the Kubernetes Konvoy pack by using the following Terraform code.
 
 ```hcl
 data "spectrocloud_registry" "public_registry" {

@@ -55,8 +55,8 @@ day 2 management.
 
 Palette has the richest coverage in supported environments that includes:
 
-- Public Clouds: AWS, Azure, Google Cloud and Tencent TKE. Palette supports both IaaS and managed Kubernetes services
-  AWS EKS, Azure AKS and Google GKE.
+- Public Clouds: AWS, Azure, and Google Cloud. Palette supports both IaaS and managed Kubernetes services AWS EKS, Azure
+  AKS, and Google GKE.
 - Data Centers: VMware, Nutanix, and OpenStack
 - Bare Metal: Canonical MAAS
 - Edge

@@ -41,7 +41,7 @@ attributes.
 | layer         | String    | True     | Relevant layer that this pack should be part of; such as os, k8s, cni, csi, addon                                                                                                                                                                                                                                                         |
 | addonType     | String    | False    | Addon-type must be set for packs that have the layer set to Addon. The value must be one of the following: logging, monitoring, load balancer, authentication, ingress, security. Setting a relevant correct addon type ensures packs are organized correctly on the management console making it easy for profile authors to find packs. |
 | version       | String    | True     | A Semantic version for the pack. It is recommended that the pack version be the same as the underlying integration it is being created for. For example, the version for the pack that will install Prometheus 2.3.4, should set to 2.3.4.                                                                                                |
-| cloudTypes    | Array     | True     | You can provide one or more types for a pack. Supported values are as follows: **all**, **aws**, **azure**, **gcp**, **tencent**, **vsphere**, **openstack**, **baremetal**, **maas**, **aks**, **eks**, **tke**, **edge**, **edge-native**, **coxedge**, and **libvirt** (virtualized edge).                                             |
+| cloudTypes    | Array     | True     | You can provide one or more types for a pack. Supported values are as follows: **all**, **aws**, **azure**, **gcp**, **vsphere**, **openstack**, **baremetal**, **maas**, **aks**, **eks**, **tke**, **edge**, **edge-native**, **coxedge**, and **libvirt** (virtualized edge).                                                          |
 | group         | String    | False    | Optional categorization of packs. For example, LTS can be set for Ubuntu OS packs.                                                                                                                                                                                                                                                        |
 | annotations   | Array     | False    | Optional key-value pairs required during pack installation. Typically, custom packs do not need to set annotations. Some packs like the ones for OS require annotations that need to be set with an image id.                                                                                                                             |
 | eol           | String    | False    | End of life date for integration.                                                                                                                                                                                                                                                                                                         |
@@ -85,7 +85,6 @@ The following is the JSON schema for packs. Review the schema to ensure your JSO
           "maas",
           "aks",
           "eks",
-          "tencent",
           "tke",
           "edge",
           "libvirt",
@@ -107,7 +106,6 @@ The following is the JSON schema for packs. Review the schema to ensure your JSO
         "maas",
         "aks",
         "eks",
-        "tencent",
         "tke",
         "edge",
         "libvirt",

@@ -93,3 +93,94 @@ metadata:
 data:
   feature.workloads: disable
 ```
+
+### OS Patch Fails
+
+When conducting [OS Patching](../clusters/cluster-management/os-patching.md), sometimes the patching process can time
+out and fail. This issue is due to some OS patches requiring GRUB packages. GRUB updates often require user prompts, and
+if a user prompt is required during the OS patching process, the patching process will fail.
+
+#### Debug Steps
+
+To resolve this issue, use the following steps:
+
+1. Log in to [Palette](https://console.spectrocloud.com/).
+
+2. From left **Main Menu**, select **Clusters**.
+
+3. Select the cluster that is experiencing the issue and click on its row to access the cluster details page.
+
+4. From the cluster details page, select the **Nodes** tab.
+
+5. Click on a cluster node to access its details page. Review the network information, such as the subnet and the
+   network the node is in.
+
+6. Log in to the infrastructure provider console and acquire the node IP address.
+
+7. SSH into one of the cluster nodes and issue the following command.
+
+   ```shell
+   rm /var/cache/debconf/config.dat && \
+   dpkg --configure -a
+   ```
+
+8. A prompt may appear asking you to select the boot device. Select the appropriate boot device and press **Enter**.
+
+   :::tip
+
+   If you are unsure of the boot device, use a disk utility such as `lsblk` or `fdisk` to identify the boot device.
+   Below is an example of using `lsblk` to identify the boot device. The output is abbreviated for brevity.
+
+   ```shell
+   lsblk --output NAME,TYPE,MOUNTPOINT
+   ```
+
+   ```shell {10} hideClipboard
+   NAME    TYPE MOUNTPOINT
+   fd0     disk
+   loop0   loop /snap/core20/1974
+   ...
+   loop10  loop /snap/snapd/20092
+   loop11  loop /snap/snapd/20290
+   sda     disk
+   ├─sda1  part /
+   ├─sda14 part
+   └─sda15 part /boot/efi
+   sr0     rom
+   ```
+
+   The highlighted line displays the boot device. In this example, the boot device is `sda15`, mounted at `/boot/efi`.
+   The boot device may be different for your node.
+
+   :::
+
+9. Repeat the previous step for all nodes in the cluster.
+
+### Scenario - Remove Deprecated Cloud Providers
+
+If you want to remove unsupported Custom Resource Definitions (CRDs) for deprecated cloud providers in your Kubernetes
+workload cluster, you can follow the steps below.
+
+#### Debug Steps
+
+1. Open a terminal session that has [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) installed.
+
+2. Set up your terminal session to use the kubeconfig file for your Kubernetes workload cluster. You can find the
+   kubeconfig for your cluster in the Palette UI by visiting the cluster's details page. Check out the
+   [Access Cluster with CLI](../clusters/cluster-management/palette-webctl.md#access-cluster-with-cli) guide for
+   guidance on how to set up your terminal session to use the kubeconfig file.
+
+3. Issue the following command to list the CRDs in your target cluster.
+
+   ```shell
+   kubectl get crd
+   ```
+
+4. Identify the CRDs for the deprecated cloud providers you want to remove. For example, to remove the Tencent Cloud
+   CRD, issue the following command.
+
+   ```shell
+   kubectl delete crd tencentcloudconfigs.cluster.spectrocloud.com
+   ```
+
+Once the CRD is removed, it will not be recreated by Palette.
@@ -15,4 +15,3 @@ using with Palette and Palette VerteX today:
 - [Amazon Web Services](/clusters/public-cloud/aws/)
 - [Azure](/clusters/public-cloud/azure/)
 - [Google Cloud](/clusters/public-cloud/gcp/)
-- [Tencent](/clusters/public-cloud/tke)
@@ -189,7 +189,9 @@ function getAggregatedVersions(registries, repositories, packUidMap) {
           const previousVersiontagdata = previousVersions.find(
             (prevVersion) => prevVersion.title === commonVersion.title
           );
-          const previousVersionChildrenSet = new Set(previousVersiontagdata.children.map((verssion) => verssion.title));
+          const previousVersionChildrenSet = new Set(
+            (previousVersiontagdata.children || []).map((verssion) => verssion.title)
+          );
           const commonComputedChildren = commonVersion.children.filter((child) =>
             previousVersionChildrenSet.has(child.title)
           );
Original file line number	Diff line number	Diff line change
Expand Up		@@ -29,5 +29,3 @@ The following pages provide detailed instructions for setting up new workload cl
		- [Azure](azure/azure.md)

		- [Google Cloud](gcp/gcp.md)

		- [Tencent](tke.md)