PhanLe1010

### Reproducing steps: 1. Install Longhorn v1.6.2/v1.7.0 (possibly v1.5.5 too) 1. Set the global setting `disable-revision-counter` to `false` 1. Create a volume with 1 replica 1. See that the `revisionCounterDisabled:...

## Test plan ### Case 1: 1. Set the global setting `disable-revision-counter` to `false` 1. Create a volume with 1 replica 1. See that the `revisionCounterDisabled: false` for both volume/engine/replica...

> I am sure I edited the replicas, but I had switched back the engine in the meantime. Doing both as suggested in the workaround worked. Thanks @docbobo for the...

Removing `stale` label. I am going to work on this ticket next

Adding the PR in backlog milestone so that it won't stale

Sorry for the delay. I updated the server and push the PR https://github.com/longhorn/longhorn/pull/9753

From the code perspective, there is no deprecated/removed API in K8s v1.31 or 1.32 that Longhorn uses. So we should be good if QA verification passes. Ref https://kubernetes.io/docs/reference/using-api/deprecation-guide/

Btw, could we test the support bundle downloading as part of the test? Support bundle usually touches many API resources and has higher chance of failure if some API is...

I will review this ~~today~~ on Monday

> Instead of performing checks only during startup, we can introduce conditions in nodes.longhorn.io to record the status of necessary packages, utilities, and demons. These conditions can be periodically checked...