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

Adding gateway-api category and age column to CRDs #592

Merged
merged 1 commit into from
Apr 8, 2021

Conversation

robscott
Copy link
Member

@robscott robscott commented Mar 19, 2021

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
This adds a gateway-api category to our CRDs as well as a new "age" column for "kubectl get" output.
Screen Shot 2021-03-19 at 3 06 04 PM

Which issue(s) this PR fixes:
Fixes #589
Also inspired by #588

Does this PR introduce a user-facing change?:

* Gateway API CRDs are not part of the "gateway-api" category. Running "kubectl get gateway-api" now returns all Gateway API resources.
* Each Gateway API resource now includes an "Age" column in "kubectl get" output.

@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Mar 19, 2021
@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 19, 2021
@robscott robscott changed the title Adding gateway-api categorie and creation timestamp column to CRDs Adding gateway-api categorie and age column to CRDs Mar 19, 2021
@robscott robscott changed the title Adding gateway-api categorie and age column to CRDs Adding gateway-api category and age column to CRDs Mar 19, 2021
@robscott robscott added this to the v0.3.0 milestone Mar 24, 2021
Copy link
Contributor

@stevesloka stevesloka left a comment

Choose a reason for hiding this comment

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

Nice work! 🎉

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: howardjohn, robscott, stevesloka

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@hbagdi
Copy link
Contributor

hbagdi commented Mar 30, 2021

@robscott Any reason for leaving BackendPolicy out?
Other than that, LGTM.

@robscott
Copy link
Member Author

robscott commented Apr 7, 2021

Thanks for catching that @hbagdi! BackendPolicy is included now.

@youngnick
Copy link
Contributor

This is really great, nice work @robscott.

@danehans
Copy link
Contributor

danehans commented Apr 8, 2021

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 8, 2021
@k8s-ci-robot k8s-ci-robot merged commit d054970 into kubernetes-sigs:master Apr 8, 2021
@robscott robscott deleted the crd-categories branch January 8, 2022 01:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
No open projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Add categories to CRDs
7 participants