Add ingress status update functionality to support various deployment modes
- Introduced `ingressStatus` configuration in Helm values to enable status updates and customize deployment modes (auto, daemonset, nodeport, clusterip). - Implemented logic in the processor to detect deployment mode, retrieve ingress addresses, and update ingress status dynamically. - Updated Kubernetes manifests to grant required permissions for `ingresses/status` operations and pass necessary environment variables for configuration. - Adjusted Helm templates and associated Kubernetes examples to reflect the new ingress status update capability.
This commit is contained in:
parent
c8f8320cfe
commit
542fab1607
8 changed files with 312 additions and 37 deletions
|
|
@ -38,6 +38,17 @@ ingressClass:
|
|||
# Additional annotations for the IngressClass
|
||||
annotations: {}
|
||||
|
||||
# Ingress status update configuration
|
||||
ingressStatus:
|
||||
# Enable updating ingress status with load balancer IPs
|
||||
enabled: true
|
||||
# Deployment mode: auto (detect), daemonset, nodeport, or clusterip
|
||||
deploymentMode: auto
|
||||
# External hostname override (for ClusterIP mode without LoadBalancer)
|
||||
externalHostname: ""
|
||||
# How often to update status (seconds)
|
||||
updateInterval: 30
|
||||
|
||||
podAnnotations: {}
|
||||
|
||||
podSecurityContext: {}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue