> ## Documentation Index
> Fetch the complete documentation index at: https://densify-sync-changelog-2.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Resolved Issues

The following page provides details of resolved issues, listed by release.

## Kubex Resolved Issues

Issues resolved in each release are listed below:

<Accordion title="3.6.0 October 1, 2025">
  * **Container Optimization**
    * "Rename View" not working on Analysis Details table
    * Policy not displayed on the policy tab for an individual container
    * Incorrect units for CPU & Memory in Spend Breakdown modal
    * Business attributes not showing in Analysis Details table
    * "Policy Comparison" view showing no data
  * **Cloud Optimization**
    * Incorrect "Discovery Date" for Azure systems
</Accordion>

<Accordion title="3.4.0 July 9, 2025">
  * **Container Optimization**
    * Incorrect values in custom views with data aggregation.
    * Discrepancy between recommended ASG/VMSS values in the UI and API.
</Accordion>

<Accordion title="3.2.0 June 11, 2025">
  * **Container Optimization**
    * Missing link between the node group and its containers.
</Accordion>

<Accordion title="3.0 April 23, 2025">
  * **Container Optimization**
    * Viewing Kubex on various screen sizes.
    * Inconsistencies in Kubex view/filter tree viewer counts.
    * Incorrect memory conversion when using the API.
</Accordion>

## Data Forwarder Resolved Issues

<Accordion title="4.2.0 - May 15, 2024 ">
  * Data forwarder fails on HPA configured to scale on more than one metric.
</Accordion>

<Accordion title="4.1.3 - April 1, 2024">
  * Nodes not being identified correctly and not being linked to their containers.
</Accordion>

<Accordion title="4.1.2 - March 17, 2024 ">
  * Node utilization exceeding 100%.
</Accordion>

<Accordion title="4.1.1 - November 27, 2024 ">
  * CPU/Memory reservation percent value exceeding 100%. This value is calculated for nodes, node groups and clusters.
</Accordion>

<Accordion title="4.1.0 - September 19, 2024 ">
  * Namespaces missing containers.
</Accordion>

<Accordion title="4.0.0 - May 28, 2024 ">
  * 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.
</Accordion>

## Kubex Automation Engine Resolved Issues (Legacy)

<Note>
  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).
</Note>

### Legacy Kubex Automation Controller Resolved Issues

<Accordion title="1.0.8 - December 12, 2025">
  * 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.
</Accordion>

<Accordion title="1.0.7 - December 11, 2025">
  * 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.
</Accordion>

<Accordion title="1.0.6 - December 9, 2025">
  * Issue where the mutating webhook was being triggered unnecessarily during pod update operations, causing increased API server load.
</Accordion>

<Accordion title="1.0.4 - November 4, 2025">
  * 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.
</Accordion>

<Accordion title="1.0.3 - October 31, 2025">
  * Issue where environment variables lacked namespace context, complicating multi-namespace deployments and troubleshooting.
</Accordion>

<Accordion title="1.0.1 - August 22, 2025">
  * 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.
</Accordion>