Tags EBS volumes when the PVC is created
100K+
It's a simple pod that checks if AWS EBS volumes created by K8s have the AWS tags required.
On your volume claims add the tags into annotations like:
annotations:
volume.beta.kubernetes.io/additional-resource-tags: Owner=Sergio,Environment=Dev
Multiple tags are , separated by default but you can override it with:
annotations:
volume.beta.kubernetes.io/additional-resource-tags-separator: ";"
You may need to grant your EC2 instances permissions to tag volumes. This is the minimal config expected:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "ec2:DescribeVolumes",
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"ec2:CreateTags"
],
"Resource": "arn:aws:ec2:*:*:volume/*",
"Condition": {
"StringEquals": {
"ec2:CreateAction" : "CreateTags"
}
}
}
]
}
See kube-tagger.yaml for an example deployment.
kubectl apply -f https://raw.githubusercontent.com/sergiorua/kube-tagger/master/kube-tagger.yaml
helm repo add sergiorua https://sergiorua.github.io/helm-charts/
helm upgrade --install kube-tagger sergiorua/kube-tagger
| Key | Type | Default | Description |
|---|---|---|---|
| affinity | object | {} | |
| extraEnv | object | {} | |
| global.name | string | "kube-tagger" | |
| global.namespace | string | "kube-system" | |
| image.backoffLimit | int | 3 | |
| image.containerPort | int | 8080 | |
| image.namespace | string | "kube-system" | |
| image.pullPolicy | string | "IfNotPresent" | |
| image.repository | string | "sergrua/kube-tagger" | |
| image.tag | string | "release-0.0.9" | |
| nodeSelector | object | {} | |
| podAnnotations | object | {} | |
| rbac.create | bool | true | |
| rbac.pspEnabled | bool | false | |
| replicas | int | 1 | |
| resources | object | {} | |
| serviceAccount.annotations | object | {} | |
| serviceAccount.create | bool | true | |
| tolerations | list | [] |
Content type
Image
Digest
Size
64.6 MB
Last updated
over 6 years ago
docker pull sergrua/kube-tagger