teleport

Chainguard Container for teleport

Teleport is an access management platform designed to provide secure and unified access to various infrastructure resources such as SSH, Kubernetes clusters, databases, and web applications

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/teleport:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Usage

There are several ways of installing and configuring Teleport. To access the whole available installation methods and configurations, visit the Teleport Installation documentation.

For example this guide shows how to run Teleport in a Docker container: https://goteleport.com/docs/installation/#example-of-running-a-teleport-container

1. Run teleport configure from the Teleport container to generate a configuration file. This sets the container's name to localhost so your browser can trust the Proxy Service's self-signed TLS certificate:

docker run --hostname localhost --rm \
  --entrypoint=/usr/local/bin/teleport \
  cgr.dev/ORGANIZATION/teleport:latest configure --roles=proxy,auth > ~/teleport/config/teleport.yaml

2. Start the Teleport container:

docker run --hostname localhost --name teleport \
  -v ~/teleport/config:/etc/teleport \
  -v ~/teleport/data:/var/lib/teleport \
  -p 3025:3025 -p 3080:3080 \
  cgr.dev/chainguard/teleport:latest

3. From there, open another terminal and make sure your Teleport container's web API is functioning as intended:

curl --insecure https://localhost:3080/webapi/ping

You should see JSON output similar to the following:

{
  "auth": {
    "type": "local",
    "second_factor": "otp",
    "preferred_local_mfa": "otp",
    "local": {
      "name": ""
    },
    "private_key_policy": "none",
    "device_trust_disabled": true,
    "has_motd": false
  },
  "proxy": {
    "kube": {
      "enabled": true,
      "listen_addr": "0.0.0.0:3080"
    },
    "ssh": {
      "listen_addr": "0.0.0.0:3080",
      "tunnel_listen_addr": "0.0.0.0:3080",
      "web_listen_addr": "0.0.0.0:3080"
    },
    "db": {
      "postgres_listen_addr": "0.0.0.0:3080",
      "mysql_listen_addr": "0.0.0.0:3080"
    },
    "tls_routing_enabled": true
  },
  "server_version": "12.1.5",
  "min_client_version": "11.0.0",
  "cluster_name": "localhost",
  "automatic_upgrades": false
}

Helm Installation for Teleport

You can install Teleport on Kubernetes using Helm. For more information, visit the Teleport Helm Chart documentation.

Add the Helm repository and install the Teleport Helm chart:

helm repo add teleport https://charts.releases.teleport.dev
helm repo update

Then install the Teleport Helm chart:

helm install teleport-cluster teleport/teleport-cluster \
  --create-namespace \
  --namespace=teleport-cluster \
  --set image=cgr.dev/ORGANIZATION/teleport

Note: As Chainguard provides only :latest tag for public images you cannot use the :latest tag for teleportVersionOverride variable as its only accepts semver type of version number. Due to that limitation you should clone this image with semver tag and use it in the helm install command. https://github.com/gravitational/teleport/blob/1e92d5e90223fc69ca75d00da4c350808dc56c2a/examples/chart/teleport-cluster/charts/teleport-operator/templates/_helpers.tpl#L38-L40 Or you could use helm --version X for Teleport version.

teleport-kube-agent-updater

Chainguard also provides the teleport-kube-agent-updater image, which is a Kubernetes controller that manages automatic updates for Teleport agents running in Kubernetes clusters.

The updater connects to the Teleport proxy to check for new versions and performs rolling updates while validating image provenance. It's typically deployed alongside the teleport-kube-agent Helm chart.

OCI Reference: cgr.dev/ORGANIZATION/teleport-kube-agent-updater

For more information, see the Teleport Kubernetes Agent Updater documentation.

Helm Installation for teleport-kube-agent-updater

The teleport-kube-agent-updater is typically deployed using the teleport-kube-agent Helm chart. For more information, see the Teleport Kube Agent Helm Chart documentation.

Note: The Teleport Helm charts override the image tag with the appVersion from Chart.yaml, ignoring any user-provided tag. This means you cannot directly specify a custom image tag via Helm values. See: Chart.yaml appVersion Tag override in _helpers.tpl

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.