What I'd like:
AWS EC2 nodes have supported high precision clocks for many years now.
However, for applications to get access to this clock requires the aws-clockbound daemon to be running on the EC2 node.
The bottlerocket images dont contain this daemon, preventing use of the clockbound api in EKS Automatic clusters (which only use Bottlerocket) and/or any EKS clusters using Bottlerocket.
aws/clock-bound#28 (comment)
Please add the aws-clockbound daemon to the Bottlerocket image so distributed applications running on EKS Automatic clusters can take advantage of the AWS Clockbound api.
Its a shame that AWS has such amazing feature and due to Bottlerocket not installing the daemon, we are not able to use it in our applications.
Any alternatives you've considered:
Currently we had to switch from EKS Automatic clusters (which use Bottlerocket) to EKS Standard cluster with AWS Linux based with custom launch template to use Clockbound.
What I'd like:
AWS EC2 nodes have supported high precision clocks for many years now.
However, for applications to get access to this clock requires the aws-clockbound daemon to be running on the EC2 node.
The bottlerocket images dont contain this daemon, preventing use of the clockbound api in EKS Automatic clusters (which only use Bottlerocket) and/or any EKS clusters using Bottlerocket.
aws/clock-bound#28 (comment)
Please add the aws-clockbound daemon to the Bottlerocket image so distributed applications running on EKS Automatic clusters can take advantage of the AWS Clockbound api.
Its a shame that AWS has such amazing feature and due to Bottlerocket not installing the daemon, we are not able to use it in our applications.
Any alternatives you've considered:
Currently we had to switch from EKS Automatic clusters (which use Bottlerocket) to EKS Standard cluster with AWS Linux based with custom launch template to use Clockbound.