The Kubernetes command-line interface (CLI), kubectl, can be used to run commands against a Kubernetes cluster. Because ACP is a Kubernetes-compatible platform, you can use the supported kubectl binaries that ship with ACP CLI, or you can gain extended functionality by using the ac binary.
The ac binary offers the same capabilities as the kubectl binary, but extends to natively support additional ACP platform features, including:
ACP CLI provides built-in support for ACP's centralized, proxy-based multi-cluster architecture:
ac login, ac config use-session, and ac logoutac config use-cluster that make it easier to work with ACP multi-cluster environmentsACP CLI automatically routes platform-level resource types like User and Project to the global cluster, since these resources only exist at the platform level. This allows you to access them from any cluster context without manual switching. All other resources work normally with your current cluster context.
ACP CLI includes additional commands that simplify ACP platform workflows:
ac login - Authenticate to ACP platforms and configure multi-cluster accessac logout - End platform sessions and clean up configurationac config get-sessions - List all configured ACP platform sessionsac config use-session <session_name> - Switch between ACP platformsac config use-cluster <cluster_name> - Switch clusters within current sessionac namespace - Enhanced namespace management with platform context displayac config sync - Synchronize configuration with platform stateThe kubectl binary is provided as a means to support existing workflows and scripts for new ACP CLI users coming from a standard Kubernetes environment, or for those who prefer to use the kubectl CLI. Existing users of kubectl can continue to use the binary to interact with Kubernetes primitives, with no changes required to the ACP platform.
For more information about kubectl, see the kubectl documentation.