From ba6e335516d472676743ec7dd60b55e83cfc2f5c Mon Sep 17 00:00:00 2001 From: pgarousi <45374076+pgarousi@users.noreply.github.com> Date: Fri, 12 Jun 2026 13:47:21 +0100 Subject: [PATCH] docs: rename Container Data Forwarder to Kubex Data Collector and fix parsing errors - Renamed Container Data Forwarder to Kubex Data Collector across all release notes - Updated component descriptions to remove module terminology - Added quick link to Kubex section in New Features page - Removed Data Forwarder, Kubex Automation Engine, and Legacy Kubex Automation Controller sections from Resolved Issues page - Removed Kubex Container Data Collector section from Third Party Software page - Fixed MDX parsing errors: - Fixed malformed

tag in Control_Console_Spectrum_Overview.mdx - Updated React import path in Carousel.mdx - Updated Carousel import path in CarouselExample.mdx - Removed unused ImageCard import in Catalog_Map_Tab.mdx --- .../Content/Cloudex/Catalog_Map_Tab.mdx | 2 - .../Control_Console_Spectrum_Overview.mdx | 4 +- .../Release_Notes/New_Features_Cloud.mdx | 18 ++--- .../Release_Notes/Resolved_Issues-Cloud.mdx | 66 ------------------- .../Third_Party_Software_Updates-Cloud.mdx | 2 - snippets/Carousel.mdx | 2 +- snippets/CarouselExample.mdx | 2 +- 7 files changed, 12 insertions(+), 84 deletions(-) diff --git a/docs-kubex/Content/Cloudex/Catalog_Map_Tab.mdx b/docs-kubex/Content/Cloudex/Catalog_Map_Tab.mdx index 60df884..6a0173a 100644 --- a/docs-kubex/Content/Cloudex/Catalog_Map_Tab.mdx +++ b/docs-kubex/Content/Cloudex/Catalog_Map_Tab.mdx @@ -2,8 +2,6 @@ title: "Catalog Map" --- -import { ImageCard } from "/snippets/ImageCard.mdx"; - ## Overview The Kubex catalog map allows you to view a range of recommended instance type options for public cloud instances. The map view shows the AWS or Azure catalog scores for the selected instance. diff --git a/docs/WebHelp_Densify/Content/Control_Console/Control_Console_Spectrum_Overview.mdx b/docs/WebHelp_Densify/Content/Control_Console/Control_Console_Spectrum_Overview.mdx index a157f08..38aef9b 100644 --- a/docs/WebHelp_Densify/Content/Control_Console/Control_Console_Spectrum_Overview.mdx +++ b/docs/WebHelp_Densify/Content/Control_Console/Control_Console_Spectrum_Overview.mdx @@ -94,9 +94,7 @@ Table: Spectrum Right-click Behavior -

-Icon

- +

Icon

diff --git a/docs/WebHelp_Densify_Cloud/Content/Release_Notes/New_Features_Cloud.mdx b/docs/WebHelp_Densify_Cloud/Content/Release_Notes/New_Features_Cloud.mdx index 028411a..cd72e8e 100644 --- a/docs/WebHelp_Densify_Cloud/Content/Release_Notes/New_Features_Cloud.mdx +++ b/docs/WebHelp_Densify_Cloud/Content/Release_Notes/New_Features_Cloud.mdx @@ -4,9 +4,9 @@ title: "New Features" The following sections provide details of new features and updates introduced in each release. -- Kubex -- Features & enhancements in the latest Kubex releases. -- [Container Data Forwarder](#container-data-forwarder) -- Updates to Kubex's Container data collection module. -- [Kubex Automation Engine](#kubex-automation-engine) -- Updates to Kubex's Automation Engine module. +- [Kubex](#kubex) -- Features & enhancements in the latest Kubex releases. +- [Kubex Data Collector](#container-data-forwarder) -- Updates to the Kubex Data Collector. +- [Kubex Automation Engine](#kubex-automation-engine) -- Updates to the Kubex Automation Engine. ## Kubex @@ -1073,15 +1073,15 @@ columns -## Container Data Forwarder +## Kubex Data Collector -This section lists new features and updates to the Container Data Forwarder. +This section lists new features and updates to the Kubex Data Collector. A Helm chart bundles all of the components required for container data collection and automates the process. See [Kubex Collection Stack](https://github.com/densify-dev/helm-charts/tree/master/charts/kubex-automation-stack) for details for a single-cluster configuration. Refer to [Github repository](https://github.com/densify-dev/container-data-collection/blob/main/README.md) for samples and configuration files for multi-cluster configurations. -When deploying the Container Data Forwarder ensure that the same version is deployed for all of your clusters. See [Data Collection for Containers](../Data_Collection_for_Public_Cloud_Systems/Container_Data_Collection_Overview) +When deploying the Kubex Data Collector ensure that the same version is deployed for all of your clusters. See [Data Collection for Containers](../Data_Collection_for_Public_Cloud_Systems/Container_Data_Collection_Overview) @@ -1542,9 +1542,9 @@ When deploying the Container Data Forwarder ensure that the same version is depl - The data forwarder has been upgraded to Go 1.22, - Updated examples for both single and multiple cluster configurations are provided in the new [Github repository](https://github.com/densify-dev/container-data-collection/blob/main/README.md). - - Kubex will discontinue support of Container Data Forwarder versions 3.x.x on June 30, 2024. Contact - support@kubex.ai for details on migrating to Kubex's current version of the Container Data Forwarder. + + Kubex will discontinue support of Kubex Data Collector versions 3.x.x on June 30, 2024. Contact + support@kubex.ai for details on migrating to Kubex's current version of the Kubex Data Collector. diff --git a/docs/WebHelp_Densify_Cloud/Content/Release_Notes/Resolved_Issues-Cloud.mdx b/docs/WebHelp_Densify_Cloud/Content/Release_Notes/Resolved_Issues-Cloud.mdx index d0f5758..f124524 100644 --- a/docs/WebHelp_Densify_Cloud/Content/Release_Notes/Resolved_Issues-Cloud.mdx +++ b/docs/WebHelp_Densify_Cloud/Content/Release_Notes/Resolved_Issues-Cloud.mdx @@ -38,69 +38,3 @@ Issues resolved in each release are listed below: - Incorrect memory conversion when using the API. -## Data Forwarder Resolved Issues - - - - Data forwarder fails on HPA configured to scale on more than one metric. - - - - - Nodes not being identified correctly and not being linked to their containers. - - - - - Node utilization exceeding 100%. - - - - - CPU/Memory reservation percent value exceeding 100%. This value is calculated for nodes, node groups and clusters. - - - - - Namespaces missing containers. - - - - - Issue related to handling version changes and additions to kube-state-metrics. - - Issue with Kubernetes Resource Quota metrics collection. - - Issue in which a panic condition was encountered during collection of NodeGroups data. - - Issue related to linking of readme.md files on Docker hub. - - -## Kubex Automation Engine Resolved Issues (Legacy) - - -The Kubex Automation Controller has been deprecated and replaced by the Kubex Automation Engine. For current resolved issues, refer to the [Kubex Automation Engine CHANGELOG](https://github.com/densify-dev/helm-charts/blob/master/charts/kubex-automation-engine/CHANGELOG.md). - - -### Legacy Kubex Automation Controller Resolved Issues - - - - Issue where deployments in air-gapped or restricted network environments could not deploy the controller due to inability to pull the wait-for-Valkey init container image from public registries. - - - - - Issue where mutating webhook was triggering on pod updates in addition to pod creation, causing unnecessary processing overhead. - - Issue with API timeouts during peak loads when retrieving recommendations from the Kubex API. - - Issue where pods with `cluster-autoscaler.kubernetes.io/safe-to-evict=false` annotation could be evicted despite the safety restriction. - - Issue in mixed clusters where Windows nodes were incorrectly considered for in-place resizing, which is not supported on Windows. Windows nodes are now automatically excluded from in-place resize attempts. - - - - - Issue where the mutating webhook was being triggered unnecessarily during pod update operations, causing increased API server load. - - - - - Issue where customers using external secret management tools could not deploy the controller without allowing the Helm chart to create secrets internally. - - Issue where the controller could only be deployed in specific predefined namespaces, limiting flexibility in multi-tenant environments. - - - - - Issue where environment variables lacked namespace context, complicating multi-namespace deployments and troubleshooting. - - - - - Issue where secrets exposed through environment variables could be viewed through process listings. - - Issue where CA bundle had to be manually configured for webhook TLS certificates. - - Issue where gateway container lacked resource limits, potentially causing resource contention. - diff --git a/docs/WebHelp_Densify_Cloud/Content/Release_Notes/Third_Party_Software_Updates-Cloud.mdx b/docs/WebHelp_Densify_Cloud/Content/Release_Notes/Third_Party_Software_Updates-Cloud.mdx index 0ae3e26..af49e96 100644 --- a/docs/WebHelp_Densify_Cloud/Content/Release_Notes/Third_Party_Software_Updates-Cloud.mdx +++ b/docs/WebHelp_Densify_Cloud/Content/Release_Notes/Third_Party_Software_Updates-Cloud.mdx @@ -15,5 +15,3 @@ The full list of the third-party software libraries used by Kubex is provided he -## Kubex Container Data Collector -The list of third-party software libraries used by the Container data collection module is provided on the [Kubex GitHub](https://github.com/densify-dev/container-data-collection) page. diff --git a/snippets/Carousel.mdx b/snippets/Carousel.mdx index 94cc342..7ea334b 100644 --- a/snippets/Carousel.mdx +++ b/snippets/Carousel.mdx @@ -1,4 +1,4 @@ -import { useState, useRef, useEffect } from 'react'; +import { useState, useRef, useEffect } from '/snippets/react'; export const Carousel = ({ images = [] }) => { const [currentIndex, setCurrentIndex] = useState(0); diff --git a/snippets/CarouselExample.mdx b/snippets/CarouselExample.mdx index b97e764..42720f3 100644 --- a/snippets/CarouselExample.mdx +++ b/snippets/CarouselExample.mdx @@ -3,7 +3,7 @@ title: "Exemplo de Uso do Carousel" description: "Como usar o componente Carousel para exibir múltiplas imagens" --- -import { Carousel } from './Carousel.mdx'; +import { Carousel } from '/snippets/Carousel.mdx'; # Exemplo de Uso do Carousel