Create an informative issue (See each section, incomplete templates/issues won’t

Prerequisite: Start with what we have
Always look at the current documentation to describe the change that is needed. Use the source or portal link for Step 3:

• Use the Customer Portal:

Looking at:

https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.7/html-single/clusters/index

1.9.10.2. Resolving the problem: Cluster status changing from offline to available
To attempt to resolve this issue, complete the following steps:
Edit your ManagedCluster specification on the hub cluster by entering the following command:

oc edit managedcluster <cluster-name>

Replace cluster-name with the name of your managed cluster.
Increase the value of leaseDurationSeconds in your ManagedCluster specification. The default value is 5 minutes, but that might not be enough time to maintain the connection with the network issues. Specify a greater amount of time for the lease. For example, you can raise the setting to 20 minutes.

1. The doc is not accurate

Clarification:

I rechecked the code: we will monitor 5 subsequent lease update, and if all of them fails, we will set cluster to unknown state. The lease duration can be set larger than 10 mins. But IF you want the cluster to be detected as offline in less than 30 min, you should set it to less than 30/5 which is 6 mins.

1. - [ ] {}Mandatory{} Choose the documentation release (Published releases are refreshed ~weekly after publication).

• [ ] ACM 2.8 (upcoming release)
• [ ] MCE 2.4 (upcoming release)
  2. - [ ] {}Mandatory{} Choose the type of documentation change.
• [ ] Update to an existing topic
  3. - [ ] {}Mandatory for bugs:{} What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation:

We need to give more guidance on how to set this property and the impact

4. - [ ] {}Mandatory for GA content:{}

• [ ] Add steps and/or other important conceptual information here:
• [ ] Add {}Required access level{} for the user to complete the task here:
• [ ] Add verification at the end of the task, how does the user verify success (a command to run or a result to see?)
• [ ] Add link to dev story here:
• {}Errata release note{} version, this is NOT for regular refreshes:
  (published with Errata release)
• [ ] ACM 2.7.x
• [ ] ACM 2.8.x
• [ ] MCE 2.3x
• [ ] MCE 2.4x