Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Migrate logger from zap to klog #51

Open
jayesh-srivastava opened this issue Mar 31, 2024 · 1 comment · May be fixed by #54
Open

Migrate logger from zap to klog #51

jayesh-srivastava opened this issue Mar 31, 2024 · 1 comment · May be fixed by #54

Comments

@jayesh-srivastava
Copy link

Proposal: Migrate logger from zap to klog which is an industry used logger used in Cluster API(CAPI) and all other providers (CAPx) projects. Using klog will help in more granular control over logging as it supports --v verbosity flag in Kubernetes objects's arguments. klog will also help in bringing this provider more in-line with other CAPx projects.
@jayesh-srivastava
Copy link
Author

/assign

@jayesh-srivastava jayesh-srivastava linked a pull request Mar 31, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Migrate logger to klog spectrocloud/cluster-api-control-plane-provider-microk8s
1 participant
@jayesh-srivastava