-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Offer a general purpose ReplicatedResource for clusterset #307
Comments
Hi @tamalsaha I will let other maintainers chime in on your suggestion. But just FYI I had a similar requirement and @JustinKuli was able provide me with a clever solution here: https://gist.github.com/JustinKuli/b66d1096e1262a0bc51f8ff8f29169f8 using ocm policy addon.
Let me know if you have any questions. |
ManifestWorkResplicaSet and ClusterAddonManager has different purposes and different persona involved.
The ManagedResourceSet seems to be quite similar as what ManifestWorkResplicaSet did? |
I was referring to the part where the controller for ManifestWorkResplicaSet, ClusterAddonManager, higher-level-of-ManagedSeviceAccount are all performing one general operation: create the individual ManifestWork, ManagedClusterAddon, ManagedServiceAccount object by copying the the parent object into the cluster namespaces. This general part can be offered a single resource. The template for the parent object can have the full underlying object spec (like PodTemplate). apiVersion: cluster.open-cluster-management.io/v1beta2
kind: ManagedClusterSetResource
metadata:
name: <name>
namespace: <ns>
spec:
placementRefs:
- name: placement-byname # Name of a created Placement
template:
apiVersion:
kind:
metadata:
...
spec:
...
|
This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the |
…nt-io#307) Signed-off-by: xuezhaojun <zxue@redhat.com> Signed-off-by: xuezhaojun <zxue@redhat.com>
Signed-off-by: Wei Liu <liuweixa@redhat.com>
Describe the enhancement
Currently there are case-by-case resources to replicate Resources in the Hub cluster to spoke cluster namespaces. Examples are:
ManagedSeviceAccount
Will it make sense to support one general purpose
ManagedResourceSet
that will take a Placement andresourceTemplate
and replicate that into the cluster namespaces according to placement logic. This can handle all the above cases as far as I can understand ( i have not thought through it deeply).I am curious if this something like this was considered? If not, is this an option?
Thanks.
The text was updated successfully, but these errors were encountered: