Tagging Stack Templates and Instances

Michael Delzer Updated by Michael Delzer

Tagging is an important aspect of managing the complexity. There are several processes that allow the creation of tags.

  1. Environment creation
  2. Template creation
  3. Deployment of a Template
  • A similar process can be added as Parameters when deploying applications

Example of a Templates tags: kind=platform created-by=MDD date=July 11 2019 cloud=any repo=GitHub.com/stackdemos ca=Let's Encrypt ci=Jenkins registry=Harbor with Minio datastore=PostgreSQL storage=Minio

Stack Template tags define the abstract (what is in template and use cases supported) aspects of all instances of this stack. These tags can be used to describe use cases. They should not reflect things relating to the deployment such as region or stage of development.

Stack Instance tags are more useful to designate things such as specific groups using the template, specific stage of deployment or purpose (Dev, Test, Staging, Production, Customer, etc). Stack Instance tags can reflect regions such as the Asian instance of a stack or parts of Europe.

Example of Stack Tags: deployed-by=MDD date=July 11 2019 repo=Github.com/stacksdemo registry=Harbor with Minio storage storage=Minio datastore=PostgreSQL ca=Let's Encrypt ci=Jenkins cloud=AWS East

Consistent tagging will make it easier to understand the usage of stacks and components across the enterprise. It will enable powerful cost management capabilities as well as governance.

How did we do?

Import of OpenShift Cluster