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.

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

Add additional printer columns to Cyclops Modules #428

Open
petar-cvit opened this issue Jul 16, 2024 · 2 comments · May be fixed by #492
Open

Add additional printer columns to Cyclops Modules #428

petar-cvit opened this issue Jul 16, 2024 · 2 comments · May be fixed by #492
Assignees
Labels
controller Update on controller go Pull requests that update Go code good first issue Good for newcomers kubernetes k8s related issues

Comments

@petar-cvit
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
K8s CRDs can define which fields will be shown through kubectl using additional printer columns. Scope of the issue is to add them to the Module CRD.

A module can show which repo, path, and version it is using, as well as the reconciliation status. You can find those fields in the controller code here.

Describe the solution you'd like
You can check out kubebuilder docs on how to add additional printer columns to CRDs using go.

@petar-cvit petar-cvit added good first issue Good for newcomers go Pull requests that update Go code controller Update on controller kubernetes k8s related issues labels Jul 16, 2024
@ashish111333
Copy link
Contributor

I would like to work on this please assign it to me.

@ashish111333
Copy link
Contributor

@petar-cvit can you assign this to me.

@ashish111333 ashish111333 linked a pull request Aug 2, 2024 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
controller Update on controller go Pull requests that update Go code good first issue Good for newcomers kubernetes k8s related issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants