Brad Durrow

We had the same problem on two OKD 4.11 clusters. I had to mitigate the issue by changing our `ClusterLogging/instance` `managementState` from `Managed` to `Unmanaged`. For the first cluster it...

It seems that this is an ongoing problem for us. Last night, during a period where the etcd and API endpoints were reported slow, this problem returned. I'm not sure...

Our clusters are logging [this](https://github.com/openshift/cluster-logging-operator/blob/cbee7d1faee2841c84765361d4fdb84b1e01b0e4/internal/k8shandler/logstore.go#L412). Which looks to compare the node part of the spec to the nodes. I don't see any recent changes in code related to that code...

Could it be either that something in the deep comparison between desired and current nodes differs that is not reconciled by the reconciliation? Or when the API call to read...

I believe that this issue is related: https://github.com/jetstack/cert-manager-olm/issues/22

Here is my current workaround in GCP: https://gist.github.com/bdurrow/e90bf7949b56476d955f489a0ef605fb

For others that land here. If you installed from brew the following command is likely to resolve this issue for you: ``` brew reinstall minishift --no-quarantine ```

I offer a potential solution in PR #10.

We use yas3fs to archive files by taring them up onto the mounted filesystem and if that succeeds we remove the files. With the current behavior data loss is very...