Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Accessing cluster Events (kubectl get events)

See original GitHub issue

I’m trying to find the way to access cluster events through the api and am unable to find the right starting point. The kubectl command I’m trying to replicate is this:

kubectl get event --field-selector involvedObject.name=mypodname-69bb65fc5c-slt69

I’m sure I’m missing something obvious, if you could lead me in the right direction…

Issue Analytics

State:
Created 4 years ago
Comments:26 (17 by maintainers)

Top GitHub Comments

1reaction

brobichaudcommented, Jun 13, 2019

Got it and all builds fine. Thanks so much for being so responsive to ideas and changes! You set the standard for github repo management!

1reaction

tintoycommented, Jun 10, 2019

Not much, I can do it this afternoon (it’s 10am here in AU) if that suits. Just need to merge to master (and tag it once the build / publish succeeds) 😃

Top Results From Across the Web

kubectl get events only for a pod - kubernetes

You should first understand the data structure of the events object. You can use kubectl get events --output json to check the data...

kubectl Cheat Sheet

This page contains a list of commonly used kubectl commands and flags. Note: These instructions are for Kubernetes v1.28.

How to collect Kubernetes events

All events can be retrieved with the help of the Kubernetes API (with kubectl as well). We often use “kubectl describe” to collect...

How to Use Kubectl Get Events

To view all events happening in your cluster, simply type the following command in your terminal: · If you want to view events...

How to Watch Kubernetes Events - The Chief IO

Kubernetes events logs can be accessed directly from the cluster using Kubectl and collected or watched through a logging tool. Running the kubectl...