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

--since flag for kubectl get events #977

Closed
phisco opened this issue Nov 9, 2020 · 4 comments
Closed

--since flag for kubectl get events #977

phisco opened this issue Nov 9, 2020 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@phisco
Copy link

phisco commented Nov 9, 2020

What would you like to be added:
A --since flag for kubectl get events, similar to the one in the logs subcommand.
Why is this needed:
Given the nature of events, more similar to logs than real resources, it would make sense to have an easy way to filter events by timestamp without recurring to jq or custom scripts.

I've tried to implement it using `-o jsonpath|gotemplate=", but it doesn't seem possible, let me know if that's not the case.

Personally I would need this in a CI/CD pipeline to print a bit more context in case of failure of the helm upgrade --install command, but i think it would be a useful feature.

@phisco phisco added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 9, 2020
@k8s-ci-robot
Copy link
Contributor

@phisco: This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Nov 9, 2020
@eddiezane
Copy link
Member

@phisco valid request but I don't think we would add this to kubectl get as it would be very specific to events.

There's currently a KEP open for a new kubectl events command. Please take a look and add your thoughts there!

kubernetes/enhancements#1440

/close

@k8s-ci-robot
Copy link
Contributor

@eddiezane: Closing this issue.

In response to this:

@phisco valid request but I don't think we would add this to kubectl get as it would be very specific to events.

There's currently a KEP open for a new kubectl events command. Please take a look and add your thoughts there!

kubernetes/enhancements#1440

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@phisco
Copy link
Author

phisco commented Nov 10, 2020

Definitely agree it would be better to have a dedicated subcommand, I'll check the proposal, thanks @eddiezane!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

3 participants