EPIC Goal

• Ability to add custom (organisation specific) tags to the pod vm instances created when using peer-pods

Why is this important?

• Admins query cloud resources for reporting, billing etc based on tags. Since peer-pods create cloud instances, it should have the provision to allow setting of admin provided tags.

Scenarios

1. Cluster admin provides custom tags (key=value pairs) when configuring peer-pods as part of the peer-pods-cm configmap
2. ...

Acceptance Criteria 

(The Epic is complete when...)

1. Ability to set custom tags in the configmap and ensuring the same is added to the pod vm instance on creation
2. Documentation
3. Test cases

Additional context:

The feature is available upstream and is also available in the downstream OSC builds starting OSC 1.7.0.

This is only supported for AWS and Azure cloud provider.

It's set via TAGS key in the peer-pods-cm configMap.

For example, to add the tags key1 and key2 the peer-pods-cm configMap must be updated to add the following param.

TAGS: "key1=value1,key2=value2"