Skip to content

WIP: status for cluster and syncregistry #831

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jinjiaKarl
Copy link
Contributor

What type of PR is this?

What this PR does / why we need it:

TODO

Which issue(s) this PR fixes:

Fixes #818

@jinjiaKarl jinjiaKarl marked this pull request as draft April 4, 2025 18:36
Create(ctx, unstructuredCluster, metav1.CreateOptions{})

// Question: when use clusterapi.ClusterStatus, when use clusterv1beta1.ClusterStatus?
Copy link
Contributor Author

@jinjiaKarl jinjiaKarl Apr 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am kinda new to developing acustom apiserver and controller. Since there are internal api types and external (v1beta1) api types, can I ask which one to use in which situation?

In the syncer reconcile, it is all v1beta1 api types.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi! Karpor has two important features. One is resource insight and another is the proxy.

The api types in v1beta1 directory define the crd of special version (v1beta1), and we use it in syncing resource and insighting. The internal api types (such as pkg/kubernetes/apis/cluster/types.go) are used to proxy.

Copy link
Contributor Author

@jinjiaKarl jinjiaKarl Apr 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for explaining!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feat: Enhance cluster status and add syncregistry status
2 participants