how to use in k8s/eks

[pdeva]

is there any guidance on how to deploy this in k8s so application pods in k8s can get accurate times

[flowerinthenight]

Yes, we do indeed need some sort of guidance. In the meantime, the way we are doing this in EKS at the moment is to expose the host's /var/run/clockbound to the pods. We are using the FFI as client using the default path of the file backing the shared memory segment. Something like:

        ...
        volumeMounts:
        - mountPath: /var/run/clockbound
          name: var-run-clockbound
          readOnly: true
      volumes:
      - name: var-run-clockbound
        hostPath:
          path: /var/run/clockbound
          type: Directory

The annoying bit was making sure the ClockBound daemon is running in all nodes. We use launch templates for those via eksctl.

[pdeva]

hmm will this method work on eks auto clusters that use bottlerocket amis and are highly preconfigured

[flowerinthenight]

I don't see any options under autoModeConfig: that allows for custom launch templates. We just use managed node groups at the moment.