warjiang
warjiang
> Since this is a big design change, we want to evaluate this with the design team that works with us, so bear with us while this may take longer....
> Proposal: One possible fix for this issue could be to remove the heart from the sidebar. Move it into the main view. Maybe we can implement these two kinds...
> @warjiang Are you interested in iterating on the items mentioned here: https://github.com/kubernetes-sigs/headlamp/pull/3150#issuecomment-2880172832 ? > > > > What do you think of these ideas? I'd like to iterate the...
> Hi @joaquimrocha @warjiang, > > Do we have any update on this? sorry late for reply, a little busy recently, I'll move on this feature - first, as described...
for the `kubernetes-dashboard-api` module, follow the instructions: 1. on **member cluster**, create a serviceaccount and authorize the serviceaccount ```shell kubectl apply --kubeconfig ~/.kube/members.config --context member1 -f -
TBD for the `karmada-dashboard-api` module, currently used permissions: - read configmap from karmada-host - permission for communication with karmada-api-server references: - https://karmada.io/docs/next/administrator/security/component-permission/
> turbo daemon clean @Cypher1 You're right, execute `npx turbo daemon logs `, I also find the similar logs:  And execute `npx turbo daemon clean` to clean the daemon...
The karmada dashboard can't be installed in different namespace except karmada-system, even if you specify the override namespace in kubectl or helm, because the karmada-dashboard-api hardcoded the karmada-system namespace. I...
@370569218 would you like to implement the namespace options?
> > The karmada dashboard can't be installed in different namespace except karmada-system, even if you specify the override namespace in kubectl or helm, because the karmada-dashboard-api hardcoded the karmada-system...