Feat: Enhance cluster status and add syncregistry status

[fanfan-yu]

What would you like to be added?

Design status machine for cluster and syncregistry

Why is this needed?

Currently, we can use karpor to manage cluster lifestyle and sync special resources. However, we can not know cluster or syncregistry status in using stage. Thus, I think it is important design and implement status machine for them.

[jinjiaKarl]

Hi, I'm interested in this. In my understanding, it is to design a status machine for a resource in a cluster, such as pending, syncing. So the frontend can show the status of a resource. I am not sure if it is correct.

Could you elaborate more about this?

[fanfan-yu]

Hi, Thank you very much for attention. There are two functions:

Firstly, I would like to design an new status machine in SyncRegistry forresources which synced bykarpor`, such as pending, syncing. This will bring two advantages: 1) The frontend can show the status of a resource. 2) The backend is more convenient to find problem.

Secondly, I would like to enhance Healthy of cluster because this status is so simple which only contains true and false. I think it is better to exhibit the detail reason, such as unhealthy(disconnected).

If you are interested in this issue, you could choose one or two function. Thank you!

Please tell me freely if you have any question or new idea for issue.

[jinjiaKarl]

Thanks for your detailed explanation. I'd like to pick this up and give it a shot for implementing both.

[fanfan-yu]

Thanks! You can refer to other multi-cloud addon such as clusterpedia to design and implement.

We can discuss further if you have any question.

[jinjiaKarl]

When I run hack/update-codegen.sh, a lot of API rule violation appear, does it matter?

Generating OpenAPI definitions for cluster:v1beta1 search:v1beta1 at github.com/KusionStack/karpor/pkg/kubernetes/generated/openapi
API rule violation: list_type_missing,github.com/KusionStack/karpor/pkg/kubernetes/apis/cluster/v1beta1,ClusterAccess,CABundle
API rule violation: list_type_missing,github.com/KusionStack/karpor/pkg/kubernetes/apis/cluster/v1beta1,ClusterStatus,Conditions
API rule violation: list_type_missing,github.com/KusionStack/karpor/pkg/kubernetes/apis/cluster/v1beta1,ExecConfig,Args
API rule violation: list_type_missing,github.com/KusionStack/karpor/pkg/kubernetes/apis/cluster/v1beta1,ExecConfig,Env
...

[fanfan-yu]

Hi! It has not influence in generating api, you could ignore these in temporary.