Skip to content

K3s

Since testcontainers-go v0.21.0

Introduction

The Testcontainers module for K3s.

Adding this module to your project dependencies

Please run the following command to add the K3s module to your Go dependencies:

go get github.com/testcontainers/testcontainers-go/modules/k3s

Usage example

ctx := context.Background()

k3sContainer, err := k3s.RunContainer(ctx,
    testcontainers.WithImage("docker.io/rancher/k3s:v1.27.1-k3s1"),
)
if err != nil {
    panic(err)
}

// Clean up the container
defer func() {
    if err := k3sContainer.Terminate(ctx); err != nil {
        panic(err)
    }
}()

Module reference

The K3s module exposes one entrypoint function to create the K3s container, and this function receives two parameters:

func RunContainer(ctx context.Context, opts ...testcontainers.ContainerCustomizer) (*K3sContainer, error)
  • context.Context, the Go context.
  • testcontainers.ContainerCustomizer, a variadic argument for passing options.

Container Ports

These are the ports used by the K3s container:

defaultKubeSecurePort     = "6443/tcp"
defaultRancherWebhookPort = "8443/tcp"

Container Options

When starting the K3s container, you can pass options in a variadic way to configure it.

Image

If you need to set a different K3s Docker image, you can use testcontainers.WithImage with a valid Docker image for K3s. E.g. testcontainers.WithImage("docker.io/rancher/k3s:v1.27.1-k3s1").

Wait Strategies

If you need to set a different wait strategy for the container, you can use testcontainers.WithWaitStrategy with a valid wait strategy.

Info

The default deadline for the wait strategy is 60 seconds.

At the same time, it's possible to set a wait strategy and a custom deadline with testcontainers.WithWaitStrategyAndDeadline.

Startup Commands

  • Not available until the next release of testcontainers-go main

Testcontainers exposes the WithStartupCommand(e ...Executable) option to run arbitrary commands in the container right after it's started.

Info

To better understand how this feature works, please read the Create containers: Lifecycle Hooks documentation.

It also exports an Executable interface, defining one single method: AsCommand(), which returns a slice of strings to represent the command and positional arguments to be executed in the container.

You could use this feature to run a custom script, or to run a command that is not supported by the module right after the container is started.

Docker type modifiers

If you need an advanced configuration for the container, you can leverage the following Docker type modifiers:

  • testcontainers.WithConfigModifier
  • testcontainers.WithHostConfigModifier
  • testcontainers.WithEndpointSettingsModifier

Please read the Create containers: Advanced Settings documentation for more information.

Container Methods

The K3s container exposes the following methods:

GetKubeConfig

The GetKubeConfig method returns the K3s cluster's kubeconfig, including the server URL, to be used for connecting to the Kubernetes Rest Client API using a Kubernetes client. It'll be returned in the format of []bytes.

package k3s_test

import (
    "context"
    "fmt"

    v1 "k8s.io/apimachinery/pkg/apis/meta/v1"
    "k8s.io/client-go/kubernetes"
    "k8s.io/client-go/tools/clientcmd"

    "github.com/testcontainers/testcontainers-go"
    "github.com/testcontainers/testcontainers-go/modules/k3s"
)

func ExampleRunContainer() {
    // runK3sContainer {
    ctx := context.Background()

    k3sContainer, err := k3s.RunContainer(ctx,
        testcontainers.WithImage("docker.io/rancher/k3s:v1.27.1-k3s1"),
    )
    if err != nil {
        panic(err)
    }

    // Clean up the container
    defer func() {
        if err := k3sContainer.Terminate(ctx); err != nil {
            panic(err)
        }
    }()
    // }

    state, err := k3sContainer.State(ctx)
    if err != nil {
        panic(err)
    }

    fmt.Println(state.Running)

    kubeConfigYaml, err := k3sContainer.GetKubeConfig(ctx)
    if err != nil {
        panic(err)
    }

    restcfg, err := clientcmd.RESTConfigFromKubeConfig(kubeConfigYaml)
    if err != nil {
        panic(err)
    }

    k8s, err := kubernetes.NewForConfig(restcfg)
    if err != nil {
        panic(err)
    }

    nodes, err := k8s.CoreV1().Nodes().List(ctx, v1.ListOptions{})
    if err != nil {
        panic(err)
    }

    fmt.Println(len(nodes.Items))

    // Output:
    // true
    // 1
}

LoadImages

The LoadImages method loads a list of images into the kubernetes cluster and makes them available to pods.

This is useful for testing images generated locally without having to push them to a public docker registry or having to configure k3s to use a private registry.

The images must be already present in the node running the test. DockerProvider offers a method for pulling images, which can be used from the test code to ensure the image is present locally before loading them to the cluster.