Skip to main content
logoTetrate Patch ServiceVersion: alpha

Accessing the Patch Service

Tetrate Patch Service is hosted by Tetrate: there is nothing to install before you connect your first cluster. Tetrate provisions your organization's account and invites its users by email; you sign in and the console is ready.

A Tour of the Console​

The sidebar is the whole navigation. From top to bottom:

  1. Clusters is the view you land on after signing in. It lists every connected cluster with its last report time and open CVE count; see Viewing Your Clusters.
  2. CVEs collects the open CVE findings across your fleet, grouped by image or listed one by one. The view is read-only by design: Tetrate owns remediation. See Monitoring Vulnerabilities.
  3. Cloud Accounts connects an AWS account so the Patch Service can discover its clusters and install the agent across them; Google Cloud and Azure show as coming soon. See Connecting an AWS Account.
  4. My Repo opens your private GitOps repository on GitHub in a new tab. The link appears once Tetrate provisions the managed data plane for your organization, and every user in your customer has read access to the repository automatically. See Working with Your Repository.
  5. Download CLI opens a dialog with tetrate CLI builds for macOS and Linux. The CLI connects clusters from your terminal; see Installing the Tetrate CLI.

The console after signing in, showing the sidebar navigation on the left and the Clusters view listing connected clusters with their last report times and open CVE counts.

The Clusters view also carries the two connection entry points, Connect cluster manually and Connect from cloud account; both routes are covered in Connecting Clusters.

Next Steps​