eraser
eraser copied to clipboard
eraser-dev
🧹 Cleaning up images from Kubernetes nodes
**Describe the solution you'd like** [A clear and concise description of what you want to happen.] Use trivy github action in [test.yaml](https://github.com/eraser-dev/eraser/blob/main/.github/workflows/test.yaml) instead of downloading the binary. **Anything else you...
### What kind of request is this? None ### What is your request or suggestion? disable unused default metrics: https://github.com/eraser-dev/eraser/blob/main/main.go#L100 ### Are you willing to submit PRs to contribute to...
### What kind of request is this? Improvement of existing experience ### What is your request or suggestion? Currently, for removed images, Eraser record the removed images in logs and...
**TODO (very likely) - move logic from the `scanner` to the `collector` & `remover`** **What this PR does / why we need it**: Add support for CRI `pinned` images. `Pinned`...
### What kind of request is this? Feature ### What is your request or suggestion? I would like Eraser to add the ability to support TLS for the eraser client...
**What steps did you take and what happened:** [A clear and concise description of what the bug is.] AKS ImageCleaner user raised issue: If eraser-controller-manager pod is restarted, the ImageJob...
### Version of Eraser _No response_ ### Expected Behavior When we first get the controller_manager_config in main.go (https://github.com/eraser-dev/eraser/blob/main/main.go#L181), we get the unversioned and modified value of the configuration, but don't...
**What steps did you take and what happened:** [A clear and concise description of what the bug is.] Update https://azure.github.io/eraser/docs/architecture to reflect rename of eraser container. **What did you expect...
**What steps did you take and what happened:** [A clear and concise description of what the bug is.] ` {"level":"error","ts":1680803506.314774,"logger":"scanner","msg":"error scanning image","provider":"trivy","imageID":"sha256:20cc4e240a565a9aefdb24907d4481a2953639e95bf15fcf86854c0a5639b5f7","reference":"mcr.microsoft.com/oss/kubernetes/kube-proxy:v1.24.3-hotfix.20221216.1","error":"failed analysis: analyze error: failed to analyze layer: :...
**Describe the solution you'd like** [A clear and concise description of what you want to happen.] instead of passing in vcs info through LDFLAGS, we should migrate to use Go...