Tag inheritance from a K8S Cluster
When you assign a tag to a K8S Cluster, all of its member Instances automatically receive the tag — including Instances added later through auto-scaling.
How it works
K8S Cluster ──assign tag──▶ tag (direct)
│
▼ propagates automatically
Instance-01 (inherited)
Instance-02 (inherited)
Instance-N (inherited) ← Instance added later
Each member Instance shows the tag with an inherited label to distinguish it from a directly assigned tag.
Direct tags vs. inherited tags
| Direct tag | Inherited tag | |
|---|---|---|
| Assigned by | Admin (manually or via a Policy) | The system (from a K8S Cluster) |
| Display | A regular tag chip | A tag chip + an "inherited" label |
| Removable at the Instance level | Yes | No |
| How to remove | Remove Tags wizard | Remove the tag at the K8S Cluster |
New Instances and auto-scaling
A new Instance added to the cluster (whether through auto-scaling or manually) automatically receives all current tags. No extra action is needed.
Duplicate tags
If you assign a tag with the same key:value as one that is already inherited, the system shows a duplicate warning. The action is still allowed — the Instance will display a single record of that duplicated tag.
📝 Note: To avoid duplicates, check the inherited tab in the Manage tags drawer before assigning a direct tag.
Removing an inherited tag
Inherited tags cannot be removed at the Instance level. To remove one, you must remove the tag at the K8S Cluster — the tag then automatically disappears from all member Instances.
⚠️ Warning: Removing a tag from a K8S Cluster removes it from all member Instances at once.