-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.17, 4.18
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
We are installing a cluster with platform external and it gets installed properly but the nodeip-configuration SystemD service is disabled.
Version-Release number of selected component (if applicable):
4.17.27
How reproducible:
Always
Steps to Reproduce:
1. Run the installer with the install config:
---
apiVersion: v1
baseDomain: ionos.yourdomain.de
compute:
- architecture: amd64
hyperthreading: Enabled
name: worker
replicas: 2
controlPlane:
architecture: amd64
hyperthreading: Enabled
name: master
replicas: 3
metadata:
name: ocp
networking:
clusterNetwork:
- cidr: 10.128.0.0/14
hostPrefix: 23
machineNetwork:
- cidr: 10.7.200.0/23
networkType: OVNKubernetes
serviceNetwork:
- 172.30.0.0/16
platform:
external:
platformName: IONOS
sshKey: 'XYZ'
pullSecret: 'XYZ'
---
2. Once it is installed the nodeip-configuration service is not running.
Actual results:
Once any node in the Cluster is rebooted, kubelet is not using the statically configured IP address for the RHCOS node, as the "/etc/systemd/system/kubelet.service.d/20-nodenet.conf" file is missing and the nodeip-configuration service is not running.
Expected results:
nodeip-configuration service is running and the "/etc/systemd/system/kubelet.service.d/20-nodenet.conf" is created
Additional info:
Seems that we need some more logic in the service enablement decision (i.e. https://github.com/openshift/machine-config-operator/blob/main/templates/common/on-prem/units/nodeip-configuration.service.yaml) for Cluster with Platform External and Load Balancer configuration done on the infrastructure level.