Describe the bug
Reloader currently does not support configuring the Kubernetes Service fields ipFamilies and ipFamilyPolicy. As a result, users deploying applications in IPv6 or dual-stack Kubernetes environments cannot explicitly define the Service IP family behavior. The generated Service resources do not expose or honor these settings, limiting compatibility with clusters that require dual-stack networking configurations. Consequently, Services cannot be configured to use IPv4-only, IPv6-only, or dual-stack modes through Reloader-managed resources, resulting in incomplete support for Kubernetes Service networking features.
To Reproduce
Steps to reproduce the behavior
- Deploy Reloader in a Kubernetes/OpenShift cluster.
- inspect the generated Service resource.
- Observe that the Service does not explicitly define spec.ipFamilies or spec.ipFamilyPolicy.
- Kubernetes automatically assigns values based on the cluster's default networking configuration.
oc describe svc reloader
Name: reloader
Namespace: mantarayap
Labels: app=reloader
app.kubernetes.io/instance=reloader
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=reloader
app.kubernetes.io/version=v1.4.6
chart=reloader-2.2.0
helm.sh/chart=reloader-2.2.0
heritage=Helm
release=reloader
Annotations: meta.helm.sh/release-name: reloader
meta.helm.sh/release-namespace: test
Selector: group=com.stakater.platform,provider=stakater,version=v1.4.6
Type: ClusterIP
IP Family Policy: SingleStack
IP Families: IPv4
IP: 172.30.13.35
IPs: 172.30.13.35
Port: http 9090/TCP
TargetPort: http/TCP
Endpoints: 10.255.13.73:9090
Session Affinity: None
Events: <none>
Expected behavior
Reloader should expose configuration options for the Kubernetes Service fields ipFamilies and ipFamilyPolicy and propagate the configured values to the generated Service resource. This would allow users to explicitly control whether the Service operates in IPv4-only, IPv6-only, or dual-stack mode instead of relying on cluster defaults.
Screenshots
Environment
- Operator Version: v1.4.6
- Kubernetes/OpenShift Version: v1.33.9 / 4.20.18
Additional context
- This limitation impacts deployments running in IPv6-only and dual-stack Kubernetes/OpenShift clusters.
- Kubernetes Services natively support the ipFamilies and ipFamilyPolicy fields, but Reloader currently does not expose these configuration options.
- Support for these fields would enable users to align Service networking behavior with cluster requirements and modern dual-stack networking deployments.
- This enhancement is particularly important for environments where IPv6 or dual-stack networking is mandatory.
Describe the bug
Reloader currently does not support configuring the Kubernetes Service fields ipFamilies and ipFamilyPolicy. As a result, users deploying applications in IPv6 or dual-stack Kubernetes environments cannot explicitly define the Service IP family behavior. The generated Service resources do not expose or honor these settings, limiting compatibility with clusters that require dual-stack networking configurations. Consequently, Services cannot be configured to use IPv4-only, IPv6-only, or dual-stack modes through Reloader-managed resources, resulting in incomplete support for Kubernetes Service networking features.
To Reproduce
Steps to reproduce the behavior
Expected behavior
Reloader should expose configuration options for the Kubernetes Service fields ipFamilies and ipFamilyPolicy and propagate the configured values to the generated Service resource. This would allow users to explicitly control whether the Service operates in IPv4-only, IPv6-only, or dual-stack mode instead of relying on cluster defaults.
Screenshots
Environment
Additional context