Kubernetes in practice Annotations Kubernetes provide us annotation feature with labels. Annotations are basically words that explanations or comments on something. For example, annotation can be used to write creator's name or contact or about application it running. Labels are meant to hold limited information whereas we can have larger annotation with any resource. Annotations are way to add some extra information to the resource but it cannot be used to group or filter like labels. Overlapping Labels With labels it is easy is to group resources. But what if any label overlap, for example type = frontend is assigned to few pods with app_name_web and env_development type = frontend is assigned to few pods with app_name_web and env_development Name of particular resource will always be unique, what about setting the similar environment as production with in development, QA phase. But what about times when you wan to split objects in separate, non-overlapping groups? We may wan