[RFE] Add an option to configure clock synchronization at install time

[e-minguez]

Version

4.X

Platform:

Any platform that doesn't provide out of the box clock synchronization (RHV, OpenStack, bare metal, but maybe others)

What happened?

Chronyd can be configured at post installation time via mco or if dhcpd is configured to send clock sources it can be done automatically, but current OpenShift installation doesn't support a proper way to have clocks synchronized at installation time. This can lead to etcd issues, certificates, etc.

What you expected to happen?

Have a parameter in the install-config.yaml that allows people to configure chronyd at installation time via ignition.

How to reproduce it (as minimally and precisely as possible)?

Have an environment where clocks are not synchronized and try to install OpenShift.

Anything else we need to know?

References

etcd-io/etcd#9768
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_basic_system_settings/using-chrony-to-configure-ntp

[abhinavdahiya]

So for cloud, there are ways to use the platform itself to provide time sync. And by default the cluster should be using that, and the users should be free to configure or change it as day-2.

so can you expand and make it clear which environment you are referring to?

[e-minguez]

So for cloud, there are ways to use the platform itself to provide time sync. And by default the cluster should be using that, and the users should be free to configure or change it as day-2.

so can you expand and make it clear which environment you are referring to?

Any non cloud such as RHV, OpenStack and bare metal.

[abhinavdahiya]

So for cloud, there are ways to use the platform itself to provide time sync. And by default the cluster should be using that, and the users should be free to configure or change it as day-2.
so can you expand and make it clear which environment you are referring to?

Any non cloud such as RHV, OpenStack and bare metal.

but the original RFE has ANY platform, so can you modify this to target specify environment?

[e-minguez]

So for cloud, there are ways to use the platform itself to provide time sync. And by default the cluster should be using that, and the users should be free to configure or change it as day-2.
so can you expand and make it clear which environment you are referring to?

Any non cloud such as RHV, OpenStack and bare metal.

but the original RFE has ANY platform, so can you modify this to target specify environment?

Done

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[jan530]

Is there any plan to implement this soon?

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.