Need doc update on best practice to sync mgmt and worker nodes' timestamps using an NTP server
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What happened**:
When the mgmt and worker nodes' timestamps are out of sync, there are errors like below:
>```level=error msg=k8sError error="github.com/cilium/cilium/pkg/k8s/watchers/endpoint_slice.go:91: Failed to watch *v1beta1.EndpointSlice: failed to list *v1beta1.EndpointSlice: Unauthorized" subsys=k8s```
**What you expected to happen**:
There must be a note in the documentation that not syncing the timestamps will lead to errors and suggest a best practice to keep the timestamps in sync.
**How to reproduce it (as minimally and precisely as possible)**:
I really do not know. I heard this from someone who experienced it and so creating an issue here to keep track of the update that is needed to the documentation.
**Anything else we need to know?**:
There is already a ticket to expose the time-server settings in the cluster spec - #707 which could be a way to do it. At the moment, I think the workaround is to manually do this on the VMs.
**Environment**:
- EKS Anywhere Release:
- EKS Distro Release:
Contributor guide
Research direction
No documentation file or test is named. Review the existing EKS Anywhere documentation for node time synchronization, then read ticket #707 to understand the planned time-server settings and current VM workaround. Done means the relevant documentation explains the timestamp-related errors and states a supported best practice for keeping management and worker nodes synchronized.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100