Amir Alavi

Hi @XiShanYongYe-Chang that's exactly it. Anything we can help with? Happy to contribute

@XiShanYongYe-Chang that is correct, I accidentally propagated a system role. With that being said, `::` is valid in names for clusterrole/clusterolebinding/roles/rolebindings. See example below: ``` $ kubectl create role "foo::bar"...

Perhaps we could replace `:` with `-` instead of `.` Given that `fo----bar` is still a valid domain

``` kubectl create role "foo:::bar" --verb=get --resource=pods role.rbac.authorization.k8s.io/foo:::bar created ``` ``` kubectl label role "foo:::bar" foo---bar=test role.rbac.authorization.k8s.io/foo:::bar labeled ``` ``` kubectl get role foo:::bar -L foo---bar NAME CREATED AT FOO---BAR...

@XiShanYongYe-Chang who is a GitHub admin with permissions to do the following first: - Create a branch called `gh-pages` - Updates [GitHub Pages](https://github.com/karmada-io/karmada/settings/pages) config to match the following ![Screenshot 2024-03-01...

Also outlined here: https://github.com/helm/chart-releaser-action?tab=readme-ov-file#pre-requisites

chart-releaser supports a flag to specify a branch, but I would be hesitant to have CI automatically push to the main branch. I did not realize that karmada publishes the...

> Is this your case? In addition, I wonder how many PropagationPolicy you are gona have? @RainbowMango that's exactly the case. At the moment, we plan on having a single...

We started using discovery api to build the propagation policy and update frequently. A controller seemed overkill for us

karmada controller-manager (by default) propagates all namespaces, unless we provide a flag to skip a namespace by name or pattern. We ran into a situation where unjoining a cluster attempted...