cloudtaser-cli target fingerprint

Reads the cluster's unique fingerprint (kube-system namespace UID) and prints it. Normal simple-connect installs do not need this command; target install can use the ctb1 beacon token directly.

Use this fingerprint only for advanced/bulk pre-registration on the secret store side with 'cloudtaser-cli source register --fingerprint '.

No secret store access needed — this just reads from the local Kubernetes cluster.

Usage

cloudtaser-cli target fingerprint [flags]

Examples

# Print the cluster fingerprint
  cloudtaser-cli target fingerprint

  # Use with a specific kubeconfig
  cloudtaser-cli target fingerprint --kubeconfig ~/.kube/staging

Flags

Flag	Type	Default	Required	Description
--help, -h	bool	false	no	help for fingerprint
--kubeconfig	string	(empty)	no	path to kubeconfig file
--timeout	duration	20m0s	no	maximum time for the command to complete (default 20m0s; also CLOUDTASER_TIMEOUT env)

Subcommands

• cloudtaser-cli target fingerprint clear-latch

All commands