Skip to content

Commit cf373b1

Browse files
authored
Merge pull request #6918 from 7h3-3mp7y-m4n/examples
karmadactl: optimize endpoint format in register command help
2 parents 92db2d1 + c6905e0 commit cf373b1

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

pkg/karmadactl/register/register.go

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -68,11 +68,15 @@ var (
6868
# Register cluster into karmada control plane with Pull mode.
6969
# If '--cluster-name' isn't specified, the cluster of current-context will be used by default.
7070
%[1]s register [karmada-apiserver-endpoint] --cluster-name=<CLUSTER_NAME> --token=<TOKEN> --discovery-token-ca-cert-hash=<CA-CERT-HASH>
71-
71+
72+
# The 'karmada-apiserver-endpoint' argument is an address of the Karmada API server from which info will be fetched.
73+
# It should be provided in the format '<host>:<port>'.
74+
%[1]s register 172.18.0.2:5443 --cluster-name=<CLUSTER_NAME> --token=<TOKEN> --discovery-token-ca-cert-hash=<CA-CERT-HASH>
75+
7276
# UnsafeSkipCAVerification allows token-based discovery without CA verification via CACertHashes. This can weaken
7377
# the security of register command since other clusters can impersonate the control-plane.
74-
%[1]s register [karmada-apiserver-endpoint] --token=<TOKEN> --discovery-token-unsafe-skip-ca-verification=true
75-
`)
78+
%[1]s register [karmada-apiserver-endpoint] --token=<TOKEN> --discovery-token-unsafe-skip-ca-verification=true
79+
`)
7680
)
7781

7882
const (

0 commit comments

Comments
 (0)