Is this a BUG REPORT or FEATURE REQUEST?:
FEATURE REQUEST
What happened:
There might be a requirement where administrators wants to propagate some properties to the managed clusters. This can be a Global param as Instance ID or cluster specific parameter such as AWS Account# or cluster name.
We should think about a way to propagate this data to all the way to managed clusters. It can be as simple as a config map in the target cluster and update the config map accordingly.
What you expected to happen:
There should be a way to know some default values at the cluster side which can be managed by Administrator from central place.
How to reproduce it (as minimally and precisely as possible):
Is this a BUG REPORT or FEATURE REQUEST?: FEATURE REQUEST
What happened: There might be a requirement where administrators wants to propagate some properties to the managed clusters. This can be a Global param as Instance ID or cluster specific parameter such as AWS Account# or cluster name.
We should think about a way to propagate this data to all the way to managed clusters. It can be as simple as a config map in the target cluster and update the config map accordingly.
What you expected to happen: There should be a way to know some default values at the cluster side which can be managed by Administrator from central place.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
Other debugging information (if applicable):
$ kubectl logs