Feature: Helm Module - Cluster Inspection for Storage/Ingress Resources

[patrick-hermann-sva]

Feature Request: Helm Module - Cluster Inspection for Storage and Ingress Resources

Problem Statement

Currently, there is a need to enhance the Helm module's capabilities to perform comprehensive inspections of a given Kubernetes cluster. Specifically, the module should be able to identify and report on existing storage classes, ingress classes, and ingress domains. This functionality is crucial for gaining a clear overview of a cluster's configuration regarding persistent storage and external access management.

Proposed Solution

This feature requests the addition of a new task within the Helm module that will:

• Inspect a given Kubernetes cluster: The module should be configurable to target a specific cluster for inspection.
• Search for StorageClass resources: Identify and list all StorageClass objects defined within the cluster.
• Search for IngressClass resources: Identify and list all IngressClass objects defined within the cluster.
• Search for Ingress Domains: Extract and report on the ingress domains configured across all Ingress resources within the cluster.

Requirements

• The new task should be integrated seamlessly into the existing Helm module architecture.
• The output should be clearly structured, potentially listing the found resources and their key attributes (e.g., name, provisioner for StorageClass, controller for IngressClass, hostnames for Ingress).
• Error handling should be robust, providing informative messages if resources are not found or if there are permission issues during inspection.

Actionable Next Steps

• Define the exact scope and parameters for the new inspection task.
• Develop the logic for querying Kubernetes API for StorageClass, IngressClass, and Ingress resources.
• Implement parsing and extraction of relevant information, including ingress domains.
• Design the output format for the inspection results.
• Add unit and integration tests for the new functionality.