Users currently cannot configure certain pod-level Kubernetes primitives through the HumioCluster custom resource. This limits flexibility for deployments that require custom DNS settings or additional initialization logic.
This issue proposes adding three new optional fields to HumioClusterSpec:
initContainers: Allow additional init containers to run before the LogScale application in each pod. Independent of the existing DisableInitContainer option.dnsPolicy: Allow setting the pod-level DNS policy (ClusterFirst, ClusterFirstWithHostNet, Default, None).dnsConfig: Allow providing custom DNS configuration (nameservers, searches, options). Required when dnsPolicy is None, per the Kubernetes PodSpec contract.
The operator should validate that dnsConfig is provided when dnsPolicy is None and return a clear error if the constraint is violated.
Users currently cannot configure certain pod-level Kubernetes primitives through the HumioCluster custom resource. This limits flexibility for deployments that require custom DNS settings or additional initialization logic.
This issue proposes adding three new optional fields to
HumioClusterSpec:initContainers: Allow additional init containers to run before the LogScale application in each pod. Independent of the existing DisableInitContainer option.dnsPolicy: Allow setting the pod-level DNS policy (ClusterFirst, ClusterFirstWithHostNet, Default, None).dnsConfig: Allow providing custom DNS configuration (nameservers, searches, options). Required whendnsPolicyisNone, per the Kubernetes PodSpec contract.The operator should validate that dnsConfig is provided when dnsPolicy is None and return a clear error if the constraint is violated.