---
title: "Public Cloud Learning Sessions- OpenText Tagging Standard v2 - 20250429 170111-Meeting Recording"
type: cloud-learning
source-type: video
category: "DevOps & SRE/10_OpenText-Series"
tags:
  - OpenText
  - Tagging-Standard
date-added: 2026-04-14
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- OpenText Tagging Standard v2 - 20250429_170111-Meeting Recording.mp4"
audio-source: ""
status: summarized (Gemini 摘要)
---

# Public Cloud Learning Sessions- OpenText Tagging Standard v2 - 20250429 170111-Meeting Recording

**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- OpenText Tagging Standard v2 - 20250429_170111-Meeting Recording.mp4`

**Type:** VIDEO | **Category:** 10_OpenText-Series

**Status:** 🟡 Awaiting Whisper transcription → Summary

---

## Open Text Tagging Standard V2

Martin Rosler presented the Open Text Tagging Standard V2, emphasizing the value of standardized tags for cloud resources, container images, and Kubernetes objects. The session aimed to increase awareness of the tagging standard and prepare attendees to apply compliant tags.

The three main drivers for the standard are:
*   Saving money through cloud cost optimization.
*   Reducing risk by easily identifying technical contacts for resources.
*   Improving efficiency via automation using tags as filters and selectors.

*It is about taking resources and you will learn more in the presentation about what kinds of object and what exactly and so on.* The standard helps with cost allocation, improved security and compliance, cloud service delivery, and resource organization. Currently, Open Text manages around 3,500 cloud accounts across 48 landing zone types, highlighting the need for consistency. The tagging standard, initiated in 2023 by the Phenops team, now includes guidelines for Kubernetes objects and container images.

The scope of the tagging standard includes cloud accounts, cloud resources (compute, storage, network), Kubernetes objects (namespaces, pods, deployments, services, config maps), and container images. The standard is complementary to existing tagging practices, encouraging the adoption of standard tags alongside proprietary ones, with a gradual deprecation of the latter.

Key concepts include:
*   Using a specific lowercase syntax with underscores for cloud resources.
*   Prefixing tags to ensure unambiguous semantics (e.g., OT\_ for cloud tags, app.opentext.com for Kubernetes labels, com.opentext.image for container image tags).
*   Defining the terms customer and tenant clearly, where customer refers to the company being hosted for, and tenant represents the contractual agreement or software instance.
*   Distinguishing between environment (Open Text's perspective) and service instance (customer's perspective).

The Wiki page provides details on proposed tags, including definitions, applicability, and permitted values. Examples of tags for cloud accounts and resources include OT business unit (OTPU) and OT technical contact. Kubernetes objects have similar tags like product, customer, and environment, along with Kubernetes-specific tags like part of, name, and version. Container images include tags for product, title, description, and vendor, with special labels for base images and their versions.

*Texts are key value pairs that typically have a tag key and an optionally a key value, which you can attach to cloud resources, cloud accounts, container images, Kubernetes objects and other things.*

Best practices for applying tags include:
*   Using infrastructure as code (e.g., Terraform) to automate tag creation and maintenance.
*   Creating checks and reports to detect missing tags.
*   Avoiding storing sensitive data in tags.
*   Being cautious about mandating tags for easily derivable information (e.g., region, account ID).
*   Handling indirect creation of resources (e.g., Kubernetes creating load balancers) using annotations.
*   Being careful with tags that frequently change to minimize maintenance overhead.
