Uploaded image for project: 'Couchbase Kubernetes'
  1. Couchbase Kubernetes
  2. K8S-162

NTP sync operator's clock

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Done
    • 0.7.0
    • 1.0.0
    • operator

    Description

      (This could be minikube issue)

      The operator generates timestamps with events, conditions, and logs.  I'm seeing the timestamps are 9 minutes behind the expected current time.  Currently the only impact is tests are failing waiting for events because they are being presenting as having occurred in the past.  Another impact I can think of is debugging where the operator time is different from couchbase.

       

      Operator is running alpine linux.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            I've linked this issue to our best practices documentation. This step should be done by the administrator for all nodes in their Kubernetes cluster. There is nothing we can with the operator or our container since we inherit the clock from the machine the container runs on.

            mikew Mike Wiederhold [X] (Inactive) added a comment - I've linked this issue to our best practices documentation. This step should be done by the administrator for all nodes in their Kubernetes cluster. There is nothing we can with the operator or our container since we inherit the clock from the machine the container runs on.

            People

              tommie Tommie McAfee
              tommie Tommie McAfee
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty