yjh

> > After deploying, shall we change the context to karmada? > > The e2e failed due to the current context is not karmada. https://github.com/karmada-io/karmada/runs/7449544501?check_suite_focus=true#step:4:579 > > We shall not...

> > What do you think about it @RainbowMango? > > Do you mean we can't or inappropriate to update the E2E? I haven't looked at the logs. During deploying,...

Hi @wangyanzhao shall we move forward it? It seems still some wrong in e2e test.

Hi @wangyanzhao i picked your commit and fixed the e2e errors: #2474

@RainbowMango

> Some touches on the expressions. Thank you for your corrections.

I just look into the generator of pod. Deployment create replicaset with a suffix name [genrated by hash of its template](https://github.com/kubernetes/kubernetes/blob/release-1.24/pkg/controller/deployment/sync.go#L189), so it will create replicasets with the same name...

The usage of cacher in proxy: https://github.com/ikaven1024/karmada/blob/feature-proxy/pkg/proxy/cache/util.go#L213

Compare between Cacher and Informer: | | Cacher | Informer | |--|-----------------------|----------| | how to sync from datasource | List/Watch | List/Watch | | Get/List with resourceVersion | [support semantics...

### About the question of long pod name The generated pod name is limited to be no more than 63 chars. @RainbowMango ```go const ( // TODO: make this flexible...