Open mohamedawnallah opened 3 months ago
/cc @zhzhuang-zju @chaosi-zju
I remember there was an issue hoping to unify the cert path in all installation methods.
I remember there was an issue hoping to unify the cert path in all installation methods.
yes, we mentioned this problem in https://github.com/karmada-io/karmada/issues/5207#issuecomment-2230735165.
yet, not to unify the cert path, but to unify the secret name between different installation method.
however, since https://github.com/karmada-io/karmada/issues/5207#issuecomment-2230781857 here didn't think this is a problem, I didn't create a separate issue specifically to track it.
Please provide an in-depth description of the question you have:
I am encountering an issue while using the
hack/local-up-karmada.sh
script. The following secrets are generated in thekarmada-system
namespace within thekarmada-host
context:When I run the following command:
It fails because it expects a
karmada-cert
secret to exist in thekarmada-system
namespace within thekarmada-host
context. This expectation is set in pkg/karmadactl/options/global.go. Here is the full trace for this error:What do you think about this question?
Since
karmada-cert-secret
andkarmada-cert
contain the same data, why not use just one secret instead of duplicating it?Additional Context:
I was working on this e2e PR #5313 for the
karmadactl addons
command and had to copy thekarmada-cert-secret
tokarmada-cert
with the same content just for thekarmadactl addons enable all
command to work.Environment:
v1.10.3
v1.29.6