{"id":79420,"date":"2026-10-20T04:21:35","date_gmt":"2026-10-20T04:21:35","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=79420"},"modified":"2026-10-20T04:21:39","modified_gmt":"2026-10-20T04:21:39","slug":"how-to-install-confluent-cli-on-macos-windows-and-linux-complete-step-by-step-guide","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/how-to-install-confluent-cli-on-macos-windows-and-linux-complete-step-by-step-guide\/","title":{"rendered":"How to Install Confluent CLI on macOS, Windows, and Linux: Complete Step-by-Step Guide"},"content":{"rendered":"\n

Meta Title:<\/strong> How to Install Confluent CLI on Mac, Windows & Linux (2026)<\/p>\n\n\n\n

Meta Description:<\/strong> Learn how to install and configure Confluent CLI on macOS, Windows, Ubuntu, Debian, RHEL, and CentOS. Includes commands, login, verification, updates, and troubleshooting.<\/p>\n\n\n\n

Keywords:<\/strong> Confluent CLI installation, install Confluent CLI Mac, Confluent CLI Windows, Confluent CLI Ubuntu, Confluent Kafka CLI, Confluent Cloud CLI, Homebrew Confluent, Confluent CLI Linux<\/p>\n\n\n\n

\n\n\n\n

1. Introduction<\/h2>\n\n\n\n

The Confluent Command Line Interface (CLI) is a powerful tool for managing Apache Kafka resources, Confluent Cloud environments, clusters, topics, API keys, connectors, and other streaming infrastructure directly from a terminal.<\/p>\n\n\n\n

Instead of performing every operation through the Confluent Cloud web console, developers, DevOps engineers, platform engineers, and Kafka administrators can use the Confluent CLI to automate routine operations.<\/p>\n\n\n\n

Confluent CLI is available for:<\/p>\n\n\n\n

    \n
  • macOS:<\/strong> Intel (x86_64) and Apple Silicon (ARM64)<\/li>\n\n\n\n
  • Windows:<\/strong> 64-bit Intel\/AMD systems<\/li>\n\n\n\n
  • Linux:<\/strong> Ubuntu, Debian, RHEL, CentOS, and supported ARM64 systems<\/li>\n\n\n\n
  • Alpine Linux:<\/strong> Supported architectures using musl-compatible binaries<\/li>\n<\/ul>\n\n\n\n

    In this tutorial, we will install Confluent CLI on all three major operating systems, verify the installation, authenticate with Confluent Cloud, and troubleshoot common installation problems.<\/p>\n\n\n\n

    2. What Is Confluent CLI?<\/h2>\n\n\n\n

    Confluent CLI is the official command-line interface for interacting with Confluent Cloud and supported Confluent Platform deployments.<\/p>\n\n\n\n

    It enables administrators and developers to manage streaming infrastructure without relying entirely on the graphical user interface.<\/p>\n\n\n\n

    Key Features<\/h3>\n\n\n\n
      \n
    • Manage Confluent Cloud organizations and environments<\/li>\n\n\n\n
    • Create, list, configure, and manage Kafka clusters<\/li>\n\n\n\n
    • Manage Kafka topics<\/li>\n\n\n\n
    • Manage API keys and access permissions<\/li>\n\n\n\n
    • Work with Schema Registry<\/li>\n\n\n\n
    • Manage Kafka connectors<\/li>\n\n\n\n
    • Integrate commands into automation scripts and CI\/CD pipelines<\/li>\n\n\n\n
    • Manage supported Confluent Platform deployments<\/li>\n\n\n\n
    • Automate day-to-day Kafka administrative tasks<\/li>\n<\/ul>\n\n\n\n

      The command-line executable is named confluent<\/code>.<\/p>\n\n\n\n

      For example:<\/p>\n\n\n

      confluent version\nconfluent login\nconfluent environment list<\/span>\nconfluent kafka cluster list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      These commands check the installation, authenticate to Confluent Cloud, and retrieve information about accessible infrastructure.<\/p>\n\n\n\n
      3. Prerequisites<\/h2>\n\n\n\n
      Before installing Confluent CLI, ensure your system meets the following requirements.<\/p>\n\n\n\n
      Requirement<\/th>Details<\/th><\/tr>
      Operating system<\/td>Supported macOS, Windows, or Linux<\/td><\/tr>
      Processor<\/td>Supported 64-bit Intel\/AMD or ARM architecture<\/td><\/tr>
      Terminal<\/td>Terminal, PowerShell, Bash, or Zsh<\/td><\/tr>
      Internet<\/td>Required to download packages and access Confluent Cloud<\/td><\/tr>
      Permissions<\/td>Ability to install software or access package managers<\/td><\/tr>
      Confluent account<\/td>Required to authenticate with Confluent Cloud<\/td><\/tr>
      Linux dependencies<\/td>Compatible glibc for standard Linux binaries<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      Important:<\/strong> Recent Confluent CLI releases for glibc-based Linux require glibc 2.28 or newer. Alpine Linux uses separate musl-compatible binaries.<\/p>\n\n\n\n
      You do not need to install Apache Kafka locally just to install and use the CLI with Confluent Cloud.<\/p>\n\n\n\n
      \n\n\n\n
      4. How to Install Confluent CLI on macOS<\/h1>\n\n\n\n
      The simplest recommended approach for macOS is using the Homebrew package manager.<\/p>\n\n\n\n
      This method works on both Intel-based and Apple Silicon Macs.<\/p>\n\n\n\n
      Step 1: Open Terminal<\/h3>\n\n\n\n
      Open the Terminal application using Spotlight or navigate to:<\/p>\n\n\n\n
      Applications \u2192 Utilities \u2192 Terminal<\/p>\n\n\n\n
      Step 2: Check Your macOS Version<\/h3>\n\n\n\n
      Run:<\/p>\n\n\n
      sw_vers<\/code><\/span><\/pre>\n\n\n
      To check your processor architecture:<\/p>\n\n\n
      uname -m<\/code><\/span><\/pre>\n\n\n
      Example results:<\/p>\n\n\n
      arm64<\/code><\/span><\/pre>\n\n\n
      This indicates an Apple Silicon Mac.<\/p>\n\n\n\n
      Alternatively:<\/p>\n\n\n
      x86_64<\/code><\/span><\/pre>\n\n\n
      This indicates an Intel architecture.<\/p>\n\n\n\n
      Step 3: Check Whether Homebrew Is Installed<\/h3>\n\n\n\n
      Execute:<\/p>\n\n\n
      brew --version<\/code><\/span><\/pre>\n\n\n
      If Homebrew is installed, the command will display its version.<\/p>\n\n\n\n
      If the terminal displays:<\/p>\n\n\n
      zsh<\/span>: command not found: brew<\/code><\/span>Code language:<\/span> HTTP<\/span> (<\/span>http<\/span>)<\/span><\/small><\/pre>\n\n\n
      Install Homebrew by following the instructions on its official website:<\/p>\n\n\n\n
      \nhttps:\/\/brew.sh\n<\/div><\/figure>\n\n\n\n
      After installing Homebrew, open a new terminal and verify:<\/p>\n\n\n
      brew --version<\/code><\/span><\/pre>\n\n\n
      Step 4: Install Confluent CLI Using Homebrew<\/h3>\n\n\n\n
      Run:<\/p>\n\n\n
      brew install confluentinc\/tap\/cli<\/code><\/span><\/pre>\n\n\n
      This command installs the Confluent CLI from Confluent’s Homebrew tap.<\/p>\n\n\n\n
      Homebrew handles downloading the package and making the confluent<\/code> executable available through the configured command path.<\/p>\n\n\n\n
      Step 5: Verify the Installation<\/h3>\n\n\n\n
      Run:<\/p>\n\n\n
      confluent version<\/code><\/span><\/pre>\n\n\n
      You should see output containing the installed CLI version, build information, and operating system architecture.<\/p>\n\n\n\n
      Example structure:<\/p>\n\n\n
      confluent - Confluent CLI\n\nVersion<\/span>:     vX.Y.Z\nGit Ref:     ...\nBuild Date<\/span>:  ...\nGo Version:  ... (darwin\/arm64)<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      The version and build details will depend on the release installed.<\/p>\n\n\n\n
      Step 6: Find the Installed Executable<\/h3>\n\n\n\n
      Execute:<\/p>\n\n\n
      which confluent<\/code><\/span><\/pre>\n\n\n
      Or:<\/p>\n\n\n
      command -v confluent<\/code><\/span><\/pre>\n\n\n
      The command should return the executable’s location.<\/p>\n\n\n\n
      For example, Homebrew’s command path may be under \/opt\/homebrew\/bin<\/code> on Apple Silicon or \/usr\/local\/bin<\/code> on Intel Macs.<\/p>\n\n\n\n
      The exact path depends on the Homebrew installation.<\/p>\n\n\n\n
      Step 7: Test the CLI<\/h3>\n\n\n\n
      Run:<\/p>\n\n\n
      confluent --help<\/code><\/span><\/pre>\n\n\n
      If the command displays the available commands and options, the executable is working.<\/p>\n\n\n\n
      Confluent CLI is now installed on macOS.<\/strong><\/p>\n\n\n\n
      5. Alternative macOS Installation Without Homebrew<\/h2>\n\n\n\n
      Confluent also provides standalone binaries and an installation script.<\/p>\n\n\n\n
      If you prefer not to use Homebrew, the following official script can download the appropriate release for your operating system and architecture:<\/p>\n\n\n
      curl -sL --http1.1<\/span> https:\/\/cnfl.io\/cli | sh -s -- latest<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Before running scripts downloaded from the internet, review their contents and ensure they originate from a trusted source.<\/p>\n\n\n\n
      Once installation is complete, ensure the directory containing the downloaded executable is included in your PATH<\/code>.<\/p>\n\n\n\n
      Then verify:<\/p>\n\n\n
      confluent version<\/code><\/span><\/pre>\n\n\n
      You can also download the appropriate Darwin ARM64 or AMD64 archive from:<\/p>\n\n\n\n
      \nhttps:\/\/github.com\/confluentinc\/cli\/releases\/latest\n<\/div><\/figure>\n\n\n\n
      For routine workstation installations, Homebrew is generally easier to maintain.<\/p>\n\n\n\n
      \n\n\n\n
      6. How to Install Confluent CLI on Windows 10\/11<\/h1>\n\n\n\n
      Windows users can install Confluent CLI using the official standalone ZIP package.<\/p>\n\n\n\n
      The native Windows release supports 64-bit Intel\/AMD architecture.<\/p>\n\n\n\n
      Step 1: Open PowerShell<\/h3>\n\n\n\n
      Open Windows PowerShell or PowerShell 7.<\/p>\n\n\n\n
      To inspect your operating system architecture, execute:<\/p>\n\n\n
      [System.Runtime.InteropServices.RuntimeInformation]<\/span>::OSArchitecture<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      For a supported native Windows installation, the result should be:<\/p>\n\n\n
      X64<\/code><\/span><\/pre>\n\n\n
      Step 2: Download the Confluent CLI<\/h3>\n\n\n\n
      Open the official GitHub releases page:<\/p>\n\n\n\n
      \nhttps:\/\/github.com\/confluentinc\/cli\/releases\/latest\n<\/div><\/figure>\n\n\n\n
      Locate the Windows archive named similarly to:<\/p>\n\n\n
      confluent_<version<\/span>><\/span>_windows_amd64.zip<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
      Here, <version><\/code> represents the actual release version.<\/p>\n\n\n\n
      Download the ZIP file into your Downloads folder.<\/p>\n\n\n\n
      Step 3: Create an Installation Directory<\/h3>\n\n\n\n
      For this tutorial, we will store the CLI under the current user’s profile.<\/p>\n\n\n\n
      Open PowerShell and execute:<\/p>\n\n\n
      $installDir = Join-Path $HOME \"Tools\\ConfluentCLI\"<\/span>\n\nNew<\/span>-Item -ItemType Directory -Path $installDir -Force<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      This creates a dedicated directory without requiring a system-wide installation.<\/p>\n\n\n\n
      Step 4: Extract the Downloaded ZIP<\/h3>\n\n\n\n
      Locate the downloaded archive:<\/p>\n\n\n
      Get-ChildItem \"$HOME\\Downloads\\confluent_*_windows_amd64.zip\"<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Select the most recently downloaded matching archive:<\/p>\n\n\n
      $zip = Get-ChildItem \"$HOME\\Downloads\\confluent_*_windows_amd64.zip\"<\/span> |\n    Sort-Object<\/span> LastWriteTime -Descending |\n    Select-Object<\/span> -First 1<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Extract it:<\/p>\n\n\n
      Expand-Archive -Path $zip.FullName -DestinationPath $installDir -Force<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      The extracted package should contain confluent.exe<\/code>.<\/p>\n\n\n\n
      Step 5: Verify the Executable<\/h3>\n\n\n\n
      Run:<\/p>\n\n\n
      & \"$installDir\\confluent.exe\"<\/span> version<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      A successful installation displays the CLI version and related build information.<\/p>\n\n\n\n
      Step 6: Add Confluent CLI to Windows PATH<\/h3>\n\n\n\n
      Adding the executable’s directory to PATH<\/code> allows you to run confluent<\/code> from any directory.<\/p>\n\n\n\n
      Use the following PowerShell commands:<\/p>\n\n\n
      $userPath = [Environment]::GetEnvironmentVariable(\"Path\"<\/span>, \"User\"<\/span>)\n\nif<\/span> (($userPath -split \";\"<\/span>) -notcontains $installDir) {\n    $newPath = ($userPath.TrimEnd(\";\"<\/span>) + \";\"<\/span> + $installDir).TrimStart(\";\"<\/span>)\n\n    [Environment]::SetEnvironmentVariable(\n        \"Path\"<\/span>,\n        $newPath,\n        \"User\"<\/span>\n    )\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Now update the current PowerShell session:<\/p>\n\n\n
      $env:Path += \";$installDir\"<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      The persistent user-level setting will also be available in newly opened terminal sessions.<\/p>\n\n\n\n
      Alternative graphical method:<\/strong><\/p>\n\n\n\n
        \n
      1. Open Windows Environment Variables.<\/li>\n\n\n\n
      2. Under User variables, select Path<\/code>.<\/li>\n\n\n\n
      3. Click Edit \u2192 New.<\/li>\n\n\n\n
      4. Add the directory containing confluent.exe<\/code>.<\/li>\n\n\n\n
      5. Save and open a new PowerShell terminal.<\/li>\n<\/ol>\n\n\n\n
        Step 7: Verify the Windows Installation<\/h3>\n\n\n\n
        Execute:<\/p>\n\n\n
        confluent version<\/code><\/span><\/pre>\n\n\n
        Locate the executable:<\/p>\n\n\n
        Get-Command confluent<\/code><\/span><\/pre>\n\n\n
        Display available commands:<\/p>\n\n\n
        confluent --help<\/code><\/span><\/pre>\n\n\n
        If these commands work, Confluent CLI is successfully installed on Windows.<\/p>\n\n\n\n
        \n\n\n\n
        7. How to Install Confluent CLI on Ubuntu and Debian Linux<\/h1>\n\n\n\n
        Ubuntu and Debian users can install Confluent CLI using the official APT repository.<\/p>\n\n\n\n
        Using APT makes package installation, upgrades, and removal straightforward.<\/p>\n\n\n\n
        Step 1: Check Your Linux Distribution<\/h3>\n\n\n\n
        Execute:<\/p>\n\n\n
        cat \/etc\/os-release<\/code><\/span><\/pre>\n\n\n
        Check the system architecture:<\/p>\n\n\n
        uname -m<\/code><\/span><\/pre>\n\n\n
        You may see:<\/p>\n\n\n
        x86_64<\/code><\/span><\/pre>\n\n\n
        or:<\/p>\n\n\n
        aarch64<\/code><\/span><\/pre>\n\n\n
        Also check your glibc version:<\/p>\n\n\n
        ldd --version<\/code><\/span><\/pre>\n\n\n
        Ensure your operating system meets the glibc requirements of the CLI release.<\/p>\n\n\n\n
        Step 2: Update APT Package Metadata<\/h3>\n\n\n\n
        Run:<\/p>\n\n\n
        sudo apt update<\/code><\/span><\/pre>\n\n\n
        Step 3: Install Required Dependencies<\/h3>\n\n\n\n
        Install curl and GnuPG:<\/p>\n\n\n
        sudo apt install -y curl gnupg<\/code><\/span><\/pre>\n\n\n
        These tools are required for downloading and installing the repository signing key.<\/p>\n\n\n\n
        Step 4: Create the APT Keyrings Directory<\/h3>\n\n\n\n
        Execute:<\/p>\n\n\n
        sudo mkdir -p \/etc\/apt\/keyrings<\/code><\/span><\/pre>\n\n\n
        Step 5: Import Confluent’s Repository Signing Key<\/h3>\n\n\n\n
        Run:<\/p>\n\n\n
        curl -fsSL https:\/\/packages.confluent.io\/confluent-cli\/deb\/archive.key \\<\/span>\n  | sudo gpg --dearmor -o \/etc\/apt\/keyrings\/confluent-cli.gpg<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Allow APT to read the key:<\/p>\n\n\n
        sudo chmod go+r \/etc\/apt\/keyrings\/confluent-cli.gpg<\/code><\/span><\/pre>\n\n\n
        The keyring permits APT to verify repository packages signed by the trusted Confluent repository key.<\/p>\n\n\n\n
        Step 6: Add the Confluent CLI APT Repository<\/h3>\n\n\n\n
        Run:<\/p>\n\n\n
        echo<\/span> \"deb [signed-by=\/etc\/apt\/keyrings\/confluent-cli.gpg] https:\/\/packages.confluent.io\/confluent-cli\/deb stable main\"<\/span> \\\n  | sudo tee \/etc\/apt\/sources.list<\/span>.d\/confluent-cli.list<\/span> >\/dev\/null<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        This registers the official Confluent CLI package repository.<\/p>\n\n\n\n
        Step 7: Refresh Package Metadata<\/h3>\n\n\n\n
        Execute:<\/p>\n\n\n
        sudo apt update<\/code><\/span><\/pre>\n\n\n
        APT will retrieve package metadata from the newly configured repository.<\/p>\n\n\n\n
        Step 8: Install Confluent CLI<\/h3>\n\n\n\n
        Execute:<\/p>\n\n\n
        sudo apt install -y confluent-cli<\/code><\/span><\/pre>\n\n\n
        APT downloads and installs the package along with any required dependencies.<\/p>\n\n\n\n
        Step 9: Verify the Installation<\/h3>\n\n\n\n
        Run:<\/p>\n\n\n
        confluent version<\/code><\/span><\/pre>\n\n\n
        Locate the executable:<\/p>\n\n\n
        which confluent<\/code><\/span><\/pre>\n\n\n
        You can also check the installed Debian package:<\/p>\n\n\n
        dpkg -l confluent-cli<\/code><\/span><\/pre>\n\n\n
        Step 10: Test the CLI<\/h3>\n\n\n\n
        Run:<\/p>\n\n\n
        confluent --help<\/code><\/span><\/pre>\n\n\n
        If the help page appears, the installation is complete.<\/p>\n\n\n\n
        Confluent CLI is now ready on Ubuntu or Debian.<\/strong><\/p>\n\n\n\n
        Special note for existing Confluent Platform installations:<\/strong> Confluent Platform can already provide its own CLI version. Installing an additional standalone version may cause package version conflicts or replacements. Check the existing packages and CLI compatibility before proceeding.<\/p>\n\n\n\n
        \n\n\n\n
        8. How to Install Confluent CLI on RHEL and CentOS<\/h1>\n\n\n\n
        For Red Hat Enterprise Linux and compatible CentOS systems, Confluent documents installation through the YUM package manager.<\/p>\n\n\n\n
        Step 1: Check Your Operating System<\/h3>\n\n\n\n
        Execute:<\/p>\n\n\n
        cat \/etc\/os-release<\/code><\/span><\/pre>\n\n\n
        Check the architecture:<\/p>\n\n\n
        uname -m<\/code><\/span><\/pre>\n\n\n
        Step 2: Import the Confluent RPM Signing Key<\/h3>\n\n\n\n
        Execute:<\/p>\n\n\n
        sudo rpm --import<\/span> https:\/\/packages.confluent.io\/confluent-cli\/rpm\/archive.key<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Step 3: Install Repository Management Utilities<\/h3>\n\n\n\n
        On YUM-based distributions supporting yum-utils<\/code>, execute:<\/p>\n\n\n
        sudo yum install -y yum-utils<\/code><\/span><\/pre>\n\n\n
        This provides the yum-config-manager<\/code> utility where supported.<\/p>\n\n\n\n
        Step 4: Add the Confluent CLI Repository<\/h3>\n\n\n\n
        Execute:<\/p>\n\n\n
        sudo yum-config-manager --add-repo \\\n  https<\/span>:\/\/packages.confluent.io\/confluent-cli\/rpm\/confluent-cli.repo<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        This registers the Confluent CLI RPM repository.<\/p>\n\n\n\n
        Step 5: Refresh YUM Metadata<\/h3>\n\n\n\n
        Execute:<\/p>\n\n\n
        sudo yum clean all<\/code><\/span><\/pre>\n\n\n
        Step 6: Install the Confluent CLI<\/h3>\n\n\n\n
        Run:<\/p>\n\n\n
        sudo yum install -y confluent-cli<\/code><\/span><\/pre>\n\n\n
        On newer RHEL-family systems, dnf<\/code> may serve as the package manager instead. Use the corresponding DNF repository management utilities where necessary.<\/p>\n\n\n\n
        Step 7: Verify the Installation<\/h3>\n\n\n
        confluent version<\/code><\/span><\/pre>\n\n\n
        Confirm the executable location:<\/p>\n\n\n
        command -v confluent<\/code><\/span><\/pre>\n\n\n
        Inspect the installed RPM package:<\/p>\n\n\n
        rpm -q confluent-cli<\/code><\/span><\/pre>\n\n\n
        Display help:<\/p>\n\n\n
        confluent --help<\/code><\/span><\/pre>\n\n\n
        Confluent CLI is now installed.<\/p>\n\n\n\n
        Important:<\/strong> If the system already has Confluent Platform installed, do not remove or replace its CLI package without checking package dependencies. On some installations, removing confluent-cli<\/code> also removes the confluent-platform<\/code> metapackage.<\/p>\n\n\n\n
        \n\n\n\n
        9. Alternative Installation on Linux Using a Script<\/h1>\n\n\n\n
        For Linux systems where you prefer not to configure APT or YUM repositories, Confluent provides a script-based installation method.<\/p>\n\n\n\n
        Run:<\/p>\n\n\n
        curl -sL --http1.1<\/span> https:\/\/cnfl.io\/cli | sh -s -- latest<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        This installation method identifies the system architecture and downloads an appropriate CLI binary.<\/p>\n\n\n\n
        Review the installation script before executing it in production or security-sensitive environments.<\/p>\n\n\n\n
        After installation, verify:<\/p>\n\n\n
        confluent version<\/code><\/span><\/pre>\n\n\n
        If the shell reports that the command is unavailable, locate the downloaded executable and add its directory to PATH<\/code>.<\/p>\n\n\n\n
        For example:<\/p>\n\n\n
        export<\/span> PATH=\"$HOME\/bin:$PATH\"<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        This example assumes the binary is located in $HOME\/bin<\/code>. Adjust the path to the actual installation directory.<\/p>\n\n\n\n
        For a persistent Bash configuration, add the export to ~\/.bashrc<\/code>.<\/p>\n\n\n\n
        Recommendation:<\/strong> For servers, prefer controlled, version-pinned installations and follow your organization’s package validation and change management practices.<\/p>\n\n\n\n
        \n\n\n\n
        10. How to Log In to Confluent Cloud Using the CLI<\/h1>\n\n\n\n
        After installing Confluent CLI on macOS, Windows, or Linux, the next step is authenticating with your Confluent Cloud account.<\/p>\n\n\n\n
        Step 1: Log In<\/h3>\n\n\n\n
        Execute:<\/p>\n\n\n
        confluent login<\/code><\/span><\/pre>\n\n\n
        Depending on your authentication configuration, the CLI may request credentials or initiate an SSO authentication workflow.<\/p>\n\n\n\n
        Follow the prompts to complete the login.<\/p>\n\n\n\n
        For environments using SSO without an accessible browser, Confluent also supports:<\/p>\n\n\n
        confluent login --no-browser<\/code><\/span><\/pre>\n\n\n
        This option is useful for browserless authentication workflows.<\/p>\n\n\n\n
        Step 2: List Confluent Cloud Environments<\/h3>\n\n\n\n
        Once authenticated:<\/p>\n\n\n
        confluent environment list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        This command lists the environments visible to the authenticated account.<\/p>\n\n\n\n
        Step 3: List Kafka Clusters<\/h3>\n\n\n\n
        Run:<\/p>\n\n\n
        confluent kafka cluster list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        To list clusters across accessible environments, you can use:<\/p>\n\n\n
        confluent kafka cluster list<\/span> --all<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Step 4: Explore Available Commands<\/h3>\n\n\n\n
        Execute:<\/p>\n\n\n
        confluent kafka --help<\/code><\/span><\/pre>\n\n\n
        Or:<\/p>\n\n\n
        confluent environment --help<\/code><\/span><\/pre>\n\n\n
        These commands display supported operations and their arguments.<\/p>\n\n\n\n
        Step 5: Log Out When Finished<\/h3>\n\n\n\n
        Execute:<\/p>\n\n\n
        confluent logout<\/code><\/span><\/pre>\n\n\n
        Logging out is particularly important on shared workstations.<\/p>\n\n\n\n
        11. How to Update Confluent CLI<\/h2>\n\n\n\n
        Keeping the CLI updated provides access to newer functionality, compatibility improvements, and security fixes.<\/p>\n\n\n\n
        macOS \u2014 Homebrew<\/h3>\n\n\n
        brew update\nbrew upgrade confluentinc\/tap\/cli<\/code><\/span><\/pre>\n\n\n
        Ubuntu\/Debian \u2014 APT<\/h3>\n\n\n
        sudo apt update\nsudo apt install --only-upgrade confluent-cli<\/code><\/span><\/pre>\n\n\n
        RHEL\/CentOS \u2014 YUM<\/h3>\n\n\n
        sudo yum update confluent-cli<\/code><\/span><\/pre>\n\n\n
        Standalone Installation<\/h3>\n\n\n\n
        For supported standalone installations, Confluent provides:<\/p>\n\n\n
        confluent update<\/code><\/span><\/pre>\n\n\n
        Confluent disables this update mechanism for CLI installations bundled with Confluent Platform to preserve version compatibility.<\/p>\n\n\n\n
        For installations managed by a package manager, prefer that package manager for upgrades.<\/p>\n\n\n\n
        Always verify the installed version afterward:<\/p>\n\n\n
        confluent version<\/code><\/span><\/pre>\n\n\n
        12. Troubleshooting Common Confluent CLI Installation Errors<\/h2>\n\n\n\n
        The following table summarizes frequently encountered installation problems and practical troubleshooting steps.<\/p>\n\n\n\n
        Error or symptom<\/th>Likely cause<\/th>Troubleshooting<\/th><\/tr>
        confluent: command not found<\/code><\/td>Executable missing or directory absent from PATH<\/td>Check installation path and update PATH<\/td><\/tr>
        brew: command not found<\/code><\/td>Homebrew not installed or not configured<\/td>Install\/configure Homebrew<\/td><\/tr>
        confluent is not recognized<\/code> on Windows<\/td>Windows PATH does not include the CLI directory<\/td>Add the executable directory to the user PATH<\/td><\/tr>
        Permission denied<\/code><\/td>Insufficient file execution permissions<\/td>Check executable permissions and installation location<\/td><\/tr>
        APT NO_PUBKEY<\/code> error<\/td>Signing key missing or incorrectly configured<\/td>Recheck the Confluent repository keyring and source entry<\/td><\/tr>
        GLIBC_2.28 not found<\/code><\/td>Linux libc version too old for the binary<\/td>Use a supported OS\/runtime or compatible release<\/td><\/tr>
        exec format error<\/code><\/td>Binary architecture does not match the system<\/td>Download the correct AMD64 or ARM64 binary<\/td><\/tr>
        Authentication fails<\/td>Credentials, SSO, permissions, or network issue<\/td>Review authentication settings and connectivity<\/td><\/tr>
        TLS certificate validation error<\/td>Trust chain or corporate proxy configuration issue<\/td>Inspect CA certificates and proxy configuration<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
        Troubleshooting 1: Command Not Found<\/h3>\n\n\n\n
        On macOS or Linux:<\/p>\n\n\n
        command -v confluent<\/code><\/span><\/pre>\n\n\n
        On Windows PowerShell:<\/p>\n\n\n
        Get-Command confluent<\/code><\/span><\/pre>\n\n\n
        If no executable is found, confirm the package installation and the directory listed in the system PATH<\/code>.<\/p>\n\n\n\n
        For example, on Linux:<\/p>\n\n\n
        echo<\/span> \"$PATH\"<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        On Windows:<\/p>\n\n\n
        $env:Path<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Troubleshooting 2: Multiple Confluent CLI Versions Installed<\/h3>\n\n\n\n
        Multiple installation methods can cause the shell to invoke an unexpected version.<\/p>\n\n\n\n
        On macOS\/Linux:<\/p>\n\n\n
        type -a confluent<\/code><\/span><\/pre>\n\n\n
        On Windows:<\/p>\n\n\n
        where<\/span>.exe<\/span> confluent<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        Review the displayed locations and remove or correct unwanted installations.<\/p>\n\n\n\n
        Troubleshooting 3: Linux GLIBC Compatibility<\/h3>\n\n\n\n
        Check:<\/p>\n\n\n
        ldd --version<\/code><\/span><\/pre>\n\n\n
        If the system has an older glibc version, a recent standard Linux binary may not work.<\/p>\n\n\n\n
        Use a compatible operating system or a supported CLI release. Do not manually replace core glibc libraries on a production system merely to install the CLI.<\/p>\n\n\n\n
        Troubleshooting 4: Confluent Cloud Login Problems<\/h3>\n\n\n\n
        First, confirm that the CLI is working:<\/p>\n\n\n
        confluent version<\/code><\/span><\/pre>\n\n\n
        Then check basic HTTPS connectivity to the Confluent Cloud endpoint:<\/p>\n\n\n
        curl -I https:\/\/confluent.cloud<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        An HTTP response demonstrates that the endpoint is reachable, but does not guarantee successful authentication.<\/p>\n\n\n\n
        For corporate environments, verify proxy settings, firewalls, DNS, certificate trust, and access to any required SSO endpoints.<\/p>\n\n\n\n
        Troubleshooting 5: Windows CLI Works Only From the Installation Folder<\/h3>\n\n\n\n
        This usually means the executable directory was not added to PATH<\/code>.<\/p>\n\n\n\n
        Confirm that the Path<\/code> environment variable includes the directory containing confluent.exe<\/code>.<\/p>\n\n\n\n
        Open a new PowerShell terminal after updating it and retry:<\/p>\n\n\n
        confluent version<\/code><\/span><\/pre>\n\n\n
        \n\n\n\n
        13. How to Uninstall Confluent CLI<\/h1>\n\n\n\n
        The uninstall method depends on how the CLI was installed.<\/p>\n\n\n\n
        macOS \u2014 Homebrew<\/h3>\n\n\n
        brew uninstall confluentinc\/tap\/cli<\/code><\/span><\/pre>\n\n\n
        Ubuntu\/Debian<\/h3>\n\n\n
        sudo apt remove confluent-cli<\/code><\/span><\/pre>\n\n\n
        RHEL\/CentOS<\/h3>\n\n\n
        sudo yum remove confluent-cli<\/code><\/span><\/pre>\n\n\n
        Review the proposed removal transaction before confirming, especially on servers with Confluent Platform installed.<\/p>\n\n\n\n
        Windows<\/h3>\n\n\n\n
        Remove confluent.exe<\/code> from the installation directory and remove its directory from the Windows user Path<\/code>.<\/p>\n\n\n\n
        If you also want to erase saved CLI sessions and configuration, the default configuration directory is:<\/p>\n\n\n
        ~\/.confluent\/<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        On Windows, this is located under the user’s profile directory.<\/p>\n\n\n\n
        Warning:<\/strong> Removing .confluent<\/code> deletes locally stored CLI settings and authentication state. Do this only when intentionally resetting or fully removing the CLI.<\/p>\n\n\n\n
        \n\n\n\n
        14. Confluent CLI Installation Command Cheat Sheet<\/h1>\n\n\n\n
        Platform<\/th>Main installation command or method<\/th><\/tr>
        macOS Intel<\/td>brew install confluentinc\/tap\/cli<\/code><\/td><\/tr>
        macOS Apple Silicon<\/td>brew install confluentinc\/tap\/cli<\/code><\/td><\/tr>
        Windows 10\/11<\/td>Download and extract the official Windows AMD64 ZIP<\/td><\/tr>
        Ubuntu\/Debian<\/td>Configure Confluent repository, then sudo apt install confluent-cli<\/code><\/td><\/tr>
        RHEL\/CentOS<\/td>Configure Confluent repository, then sudo yum install confluent-cli<\/code><\/td><\/tr>
        Script-based installation<\/td>curl -sL --http1.1 https:\/\/cnfl.io\/cli | sh -s -- latest<\/code><\/td><\/tr>
        Verify installation<\/td>confluent version<\/code><\/td><\/tr>
        Log in<\/td>confluent login<\/code><\/td><\/tr>
        List environments<\/td>confluent environment list<\/code><\/td><\/tr>
        List Kafka clusters<\/td>confluent kafka cluster list<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
        15. Frequently Asked Questions<\/h2>\n\n\n\n
        Is Confluent CLI free to install?<\/h3>\n\n\n\n
        Yes. You can download and install the CLI without paying an installation fee. However, Confluent Cloud services and resources may incur usage charges.<\/p>\n\n\n\n
        Do I need Java to install Confluent CLI?<\/h3>\n\n\n\n
        The standalone CLI is a prebuilt executable and does not require you to install the Java Development Kit just to run basic Confluent Cloud commands.<\/p>\n\n\n\n
        Can I install Confluent CLI on an Apple M-series Mac?<\/h3>\n\n\n\n
        Yes. Confluent provides native macOS ARM64 support for Apple Silicon Macs.<\/p>\n\n\n\n
        Does Confluent CLI work on Windows?<\/h3>\n\n\n\n
        Yes. Confluent provides a native executable for supported 64-bit Windows Intel\/AMD systems. You can run it through PowerShell or Command Prompt.<\/p>\n\n\n\n
        Can I use Confluent CLI without installing Kafka locally?<\/h3>\n\n\n\n
        Yes. For Confluent Cloud, you can authenticate directly with your cloud account and manage authorized resources remotely.<\/p>\n\n\n\n
        Is Confluent CLI the same as the Apache Kafka command-line tools?<\/h3>\n\n\n\n
        No. Apache Kafka includes utilities such as kafka-topics.sh<\/code> and kafka-console-consumer.sh<\/code>.<\/p>\n\n\n\n
        Confluent CLI is a separate interface designed for managing Confluent Cloud and supported Confluent Platform resources.<\/p>\n\n\n\n
        How do I check which Confluent CLI version is installed?<\/h3>\n\n\n\n
        Run:<\/p>\n\n\n
        confluent version<\/code><\/span><\/pre>\n\n\n
        Can I use Confluent CLI in CI\/CD pipelines?<\/h3>\n\n\n\n
        Yes. The CLI can be integrated into automated workflows. For CI\/CD systems, prefer appropriate service-account authentication, secure secret management, least-privilege access, and controlled CLI versioning rather than interactive personal-user authentication.<\/p>\n\n\n\n
        16. Best Practices<\/h2>\n\n\n\n
        When using Confluent CLI in development or production environments, follow these recommendations:<\/p>\n\n\n\n
          \n
        1. Install the CLI using official, trusted distribution methods.<\/li>\n\n\n\n
        2. Confirm your operating system architecture before downloading binaries.<\/li>\n\n\n\n
        3. Keep the CLI version compatible with the Confluent Platform version you manage.<\/li>\n\n\n\n
        4. Prefer package managers for routine workstation installations.<\/li>\n\n\n\n
        5. Pin approved CLI versions in production automation.<\/li>\n\n\n\n
        6. Never hardcode credentials or API keys in shell scripts.<\/li>\n\n\n\n
        7. Use least-privilege service accounts for automation.<\/li>\n\n\n\n
        8. Avoid storing passwords or tokens in shell history.<\/li>\n\n\n\n
        9. Verify environment and cluster selection before running administrative commands.<\/li>\n\n\n\n
        10. Use --help<\/code> to check command syntax for your installed CLI version.<\/li>\n<\/ol>\n\n\n\n
          17. Conclusion<\/h2>\n\n\n\n
          Installing the Confluent CLI is an important first step toward managing Kafka and Confluent infrastructure from the command line.<\/p>\n\n\n\n
          For macOS<\/strong>, Homebrew offers the simplest installation experience.<\/p>\n\n\n\n
          For Windows<\/strong>, downloading and configuring the official CLI executable is a straightforward approach.<\/p>\n\n\n\n
          For Ubuntu and Debian<\/strong>, the official APT repository provides convenient package management.<\/p>\n\n\n\n
          For RHEL and CentOS<\/strong>, Confluent offers an RPM repository compatible with supported YUM-based distributions.<\/p>\n\n\n\n
          After installation, three essential commands provide a useful starting point:<\/p>\n\n\n
          confluent version\nconfluent login\nconfluent environment list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
          With the CLI installed and authenticated, engineers can begin exploring Kafka clusters, automating administrative operations, and integrating Confluent Cloud into DevOps workflows.<\/p>\n\n\n\n
          \n\n\n\n
          Official References<\/h2>\n\n\n\n