Bernard Pietraga

IAC tagging for your git blame needs – Yor

yor, infrastructure as code tagging

Have you ever been in situation where you noticed some weird cloud resource or weird Kubernetes pod? Have you ever had a hard time finding respecitve owner of this resource?

Ideally this situation should not happen, with good practices in place and propper tagging enforcement. Unfortunately we are not living in perfect world, the agile manifesto of Facebook "move fast, break things" which spread to a lot of places leave a lot of things untidy. If you worked long enough in the field complex infrastructure you know what I’m reffering to.

Having proper tags/Kuberentes labels in place helps to keep mental picture of infrastructure, maintain and navigate quicker.

Yor – new free automation tool for IAC tagging

yor by Bridgecrew is free and open-source project aiming to help infrastructure engineers help to orginize their cloud and kuberentes resources. There is support for 3 big cloud providers and kuberentes.

Tracability is one of biggest problems in greenfield projects or big corporate projects.

Tracing code in the cloud can be a challenge, especially when you want to track down specific change to cloud infrastructure. One solution is to use custom tags to help track down your code. You can then use native cloud or kuberentes tools to understand the problem better.

Yor adds important information each new created resource including for example git commit sha. This might save you years after, when you will be looking why something is there in the first place. yor_trace or git_file enables you to find resource in code repostory.

It does integrate with major CI platforms and could be easly integrated with new ones. Here are documentation examples. It works with pre-commit hooks.

Why it is important to tag your cloud infrastructure?

Cloud computing has quickly become a mainstay in the modern IT landscape. It offers many benefits, such as lower costs and better agility, but one challenge it faces is how to manage and monitor resources. One solution is to tag resources so that they can be easily found and managed. In this article, we’ll look at tagging resources in Kubernetes and Amazon Web Services (AWS).

Tagging resources can be a great way to improve your management of your cloud infrastructure. For example, you could use tags to group related resources together, such as instances or services. This can make it much easier to find and manage these resources. You could also use tags to track specific changes, such as when an instance is upgraded or deleted. When you tag your resources in Kubernetes or AWS resources managed by Terraform, you can easily find and access them later. This becomes especially important when you need to troubleshoot or manage a complex cloud-based application. By tagging your resources, you can quickly identify which components are affected by a problem.

Kubernetes lets you tag both individual objects (e.g., pods) and collections of objects (e. g. crds). But this all comes at the cost of maintenance. Yor tries to fix this provinding reasonable set of functionality out of the box.