Skip to main content

diagrid k8s-operator compatibility

Report whether a namespace can migrate to Catalyst

Description​

Report whether a Kubernetes namespace can migrate to Catalyst, without changing anything.

Every Dapr resource in the namespace gets one of four results:

• supported moves across as it is • needs remediation moves across, but something must be fixed or will be lost • unsupported Catalyst has no equivalent • needs Diagrid requires a Diagrid-assisted path

It also reports what the cluster itself needs before the operator can be installed: cert-manager, and whether the Dapr CRDs already belong to something else.

The command reads your cluster and nothing else. It makes no changes, and it does not contact Catalyst — the list of supported component types is built into the CLI from the same source the platform validates against.

Run it before deciding whether to install anything: it needs no login, no network, and no operator in the cluster.

diagrid k8s-operator compatibility <namespace> [flags]

Examples​


  # Assess a namespace
  diagrid k8s-operator compatibility orders

  # Assess it for a Dapr server running in your own cluster
  diagrid k8s-operator compatibility orders --host local

Options​

      --host string         Sidecar mode to assess against: 'remote' (managed cloud) or 'local' (in-cluster). (default "remote")
      --kubeconfig string   Path to the kubeconfig file. Defaults to the standard resolution (KUBECONFIG / ~/.kube/config).
      --context string      Name of the kube context to read. Defaults to your current context.
  -h, --help                help for compatibility

SEE ALSO​

Last updated on