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

Have spegel generate k8s events to visualize usage and make debugging easier #706

Open
NissesSenap opened this issue Jan 21, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@NissesSenap
Copy link

Describe the problem to be solved

Hi

Finally, I have gotten the chance to use spegel again, and I thought it's a bit hard to know if my container is actually being pulled by spegel or not.

I can probably enable some debug log to see it, but another option would be to start using K8s events, just like GKE is doing with its image streaming.

Not priority number one, and there is a risk of it getting rather chatty and it will require access to the k8s api, which I can see that not all users want.
But as long as it's possible to disable the feature in the code and helm chart it could be a nice feature to implement.

Here you can see how GKE does it: https://cloud.google.com/kubernetes-engine/docs/how-to/image-streaming
And here is an example on how it looks in our cluster.

default                           8m11s       Normal    ImageStreaming                           node/gke-gke-green-staging-e-spot-compute2-9a17876f-jr9z                         (combined from similar events): Image gke.gcr.io/gke-metrics-collector@sha256:545f5594f9a6ee714b315897f92edeaa858b1074e4c6a38894353214907e4fe5 is backed by image streaming.
default                           8m4s        Normal    ImageStreaming                           node/gke-gke-green-staging-e-spot-compute2-9a17876f-jr9z                         Layer download failed. Layer id: "sha256:59654b79daad74c77dc2e28502ca577ba8ce73276720002234a23fc60ee92692", image: "docker.io/library/busybox@sha256:79c9716db559ffde1170a4faf04910a08d930f511e6904c4899a1f7be2abfb34"

Proposed solution to the problem

No response

@NissesSenap NissesSenap added the enhancement New feature or request label Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant