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

cbopinfo: couchbase-operator/events.yaml file missing under deployment dir

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.0.0
    • 1.0.0
    • kubernetes

    Description

      cbopinfo-20180803T190517-0700/default/deployment/couchbase-operator/events.yaml file missing in the collected logs

      Attachments

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

        Activity

          Closing this since it works as expected with k8s platform.

          ashwin.govindarajulu Ashwin Govindarajulu added a comment - Closing this since it works as expected with k8s platform.
          simon.murray Simon Murray added a comment -

          See https://github.com/kubernetes/kubernetes/issues/52521 K8S will not fix it.  We have everything we need for support in the log files already.

          simon.murray Simon Murray added a comment - See https://github.com/kubernetes/kubernetes/issues/52521 K8S will not fix it.  We have everything we need for support in the log files already.
          simon.murray Simon Murray added a comment -

          Kubernetes does not work that way, nothing we can do about it.

          If they collected every event ever their database would eventually fill up and the cluster will die.

          Likewise if we recorded every event we ever raised we'd run out of memory/disk eventually and be killed.

          simon.murray Simon Murray added a comment - Kubernetes does not work that way, nothing we can do about it. If they collected every event ever their database would eventually fill up and the cluster will die. Likewise if we recorded every event we ever raised we'd run out of memory/disk eventually and be killed.

          So why the event existence is with respect to time ?

          We should be able to get the events at any point of time to know about the last event occurred in operator.

          In real time, we should be able to get the events in the longer run.

          ashwin.govindarajulu Ashwin Govindarajulu added a comment - So why the event existence is with respect to time ? We should be able to get the events at any point of time to know about the last event occurred in operator. In real time, we should be able to get the events in the longer run.
          simon.murray Simon Murray added a comment -

          If you re-deploy the operator just before running this test I can guarantee it will fix the issue

          simon.murray Simon Murray added a comment - If you re-deploy the operator just before running this test I can guarantee it will fix the issue

          People

            ashwin.govindarajulu Ashwin Govindarajulu
            ashwin.govindarajulu Ashwin Govindarajulu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty