kubectl-blame

KO | EN

gitlite — search

#python #ai #typescript #llm #golang #rust #docker #nodejs #java #vue #pytorch #mcp #openai #open-source

(★ 154)

Show who edited resource fields.

파일 탐색기

최종 버전 다운로드 (.zip)

- - build.yml
- dependabot.yml
- - deploy.json
  - deploy.json.txt
  - deploy.yaml
  - deploy.yaml.txt
  - list.yaml
  - list.yaml.txt
  - multi-manager-list-item.yaml
  - multi-manager-list-item.yaml.txt
- blame.go
- blame_test.go
- color.go
- color_test.go
- context.go
- encoder.go
- encoder_test.go
- marshal.go
- marshal_test.go
- util.go
.gitignore
.goreleaser.yaml
.krew.yaml
go.mod
go.sum
LICENSE
main.go
Makefile
README.md

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

kubectl-blame: git-like blame for kubectl
======

![GitHub](https://img.shields.io/github/license/knight42/kubectl-blame)
![](https://github.com/knight42/kubectl-blame/actions/workflows/build.yml/badge.svg)
![GitHub last commit](https://img.shields.io/github/last-commit/knight42/kubectl-blame)

Annotate each line in the given resource's YAML with information from the managedFields
to show who last modified the field.

As long as the field `.metadata.manageFields` of the resource is set properly, this command
is able to display the manager of each field.

`kubectl-blame` can work in two ways:

1. **Directly from the cluster** — fetch and blame resources in one step:
   ```
   kubectl blame deployments my-app
   ```
2. **From piped input** — use `kubectl get` (or any command that outputs YAML/JSON) and pipe the result:
   ```
   kubectl get deployments -o yaml | kubectl blame
   ```
   This also works with Kubernetes List objects (e.g., `kind: List`), so you can pipe the output of `kubectl get` which wraps multiple resources in a List.

[![asciicast](https://asciinema.org/a/375008.svg)](https://asciinema.org/a/375008)

## Installing

| Distribution                           | Command / Link                                                         |
|----------------------------------------|------------------------------------------------------------------------|
| [Krew](https://krew.sigs.k8s.io/)      | `kubectl krew install blame`                                           |
| Pre-built binaries for macOS, Linux    | [GitHub releases](https://github.com/knight42/kubectl-blame/releases)  |

## Usage

```
# Blame pod 'foo' in default namespace
kubectl blame pods foo

# Blame deployment 'foo' and 'bar' in 'ns1' namespace
kubectl blame -n ns1 deploy foo bar

# Blame deployment 'bar' in 'ns1' namespace and hide the update time
kubectl blame -n ns1 --time none deploy bar

# Blame resources in file 'pod.yaml'(will access remote server)
kubectl blame -f pod.yaml

# Blame deployment saved in local file 'deployment.yaml'(will NOT access remote server)
kubectl blame -i deployment.yaml
# Or pipe from stdin (auto-detected)
cat deployment.yaml | kubectl blame
```

### Flags

| flag               | default    | description                                                              |
|--------------------|------------|--------------------------------------------------------------------------|
| `--time`           | `relative` | Time format. One of: `full`, `relative`, `none`.                         |
| `--color`          | `auto`     | Color output. One of: `auto`, `always`, `never`.                         |
| `--filename`, `-f` |            | Filename identifying the resource to get from a server.                  |
| `--input`, `-i`    | `auto`     | Read object from the given file. When set to `auto`, automatically read from stdin if piped. Use `-` to force reading from stdin. |

kubectl-blame

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

kubectl-blame

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README