bind cluster-identity

Synopsis

Get the cluster identity for the current Kubernetes cluster.

The cluster identity is derived from the UID of a namespace (by default kube-system). This identity is used by kube-bind to uniquely identify consumer clusters when binding to service providers.

This is a helper command for users who are not using the kube-bind web server and need to manually provide the cluster identity.

bind cluster-identity [flags]

Examples

# Get the cluster identity for the current kubeconfig context
kubectl bind cluster-identity

# Get the cluster identity using a specific kubeconfig
kubectl bind cluster-identity --kubeconfig /path/to/kubeconfig

# Get the cluster identity using a specific context
kubectl bind cluster-identity --context my-context

# Get the cluster identity from a specific namespace (default: kube-system)
kubectl bind cluster-identity --namespace my-namespace

Options

      --as-uid string                        UID to impersonate for the operation
      --certificate-authority string         Path to a cert file for the certificate authority
      --context string                       The name of the kubeconfig context to use
      --disable-compression                  If true, opt-out of response compression for all requests to the server
  -h, --help                                 help for cluster-identity
      --insecure-skip-tls-verify             If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
      --kubeconfig string                    path to the kubeconfig file
      --log-flush-frequency duration         Maximum number of seconds between log flushes (default 5s)
      --log-text-info-buffer-size quantity   [Alpha] In text format with split output streams, the info messages can be buffered for a while to increase performance. The default value of zero bytes disables buffering. The size can be specified as number of bytes (512), multiples of 1000 (1K), multiples of 1024 (2Ki), or powers of those (3M, 4G, 5Mi, 6Gi). Enable the LoggingAlphaOptions feature gate to use this.
      --log-text-split-stream                [Alpha] In text format, write error messages to stderr and info messages to stdout. The default is to write a single stream to stdout. Enable the LoggingAlphaOptions feature gate to use this.
      --logging-format string                Sets the log format. Permitted formats: "text". (default "text")
  -n, --namespace string                     namespace to use for deriving the cluster identity (default: kube-system) (default "kube-system")
      --password string                      Password for basic authentication to the API server
      --proxy-url string                     If provided, this URL will be used to connect via proxy
      --server string                        The address and port of the Kubernetes API server
      --tls-server-name string               If provided, this name will be used to validate server certificate. If this is not provided, hostname used to contact the server is used.
      --token string                         Bearer token for authentication to the API server
      --user string                          The name of the kubeconfig user to use
      --username string                      Username for basic authentication to the API server
  -v, --v Level                              number for the log level verbosity
      --vmodule pattern=N,...                comma-separated list of pattern=N settings for file-filtered logging (only works for text log format)

Options inherited from parent commands

      --add_dir_header                   If true, adds the file directory to the header of the log messages
      --alsologtostderr                  log to standard error as well as files (no effect when -logtostderr=true)
      --log_backtrace_at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
      --log_dir string                   If non-empty, write log files in this directory (no effect when -logtostderr=true)
      --log_file string                  If non-empty, use this log file (no effect when -logtostderr=true)
      --log_file_max_size uint           Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
      --logtostderr                      log to standard error instead of files (default true)
      --one_output                       If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true)
      --skip_headers                     If true, avoid header prefixes in the log messages
      --skip_log_headers                 If true, avoid headers when opening log files (no effect when -logtostderr=true)
      --stderrthreshold severity         logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2)

See Also

• bind – Open kube-bind UI or bind templates from a remote server.