Skip to main content
The following page provides details of resolved issues, listed by release.

​
Kubex Resolved Issues

Issues resolved in each release are listed below:
  • 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
  • Container Optimization
    • Incorrect values in custom views with data aggregation.
    • Discrepancy between recommended ASG/VMSS values in the UI and API.
  • Container Optimization
    • Missing link between the node group and its containers.
  • Container Optimization
    • Viewing Kubex on various screen sizes.
    • Inconsistencies in Kubex view/filter tree viewer counts.
    • 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 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.