Building and Testing

Submariner strives to be an open, welcoming community. Substantial tooling is provided to ease the contribution experience.

Standard Development Environment

Submariner provides a standard, shared environment for both development and CI that is maintained in the Shipyard project.

Learn more about working with Shipyard here.

Building and Testing

Submariner provides a set of Make targets for building and testing in the standard development environment.


To run all linting:

make lint

There are also Make targets for each type of linting:

make gitlint golangci-lint markdownlint yamllint

See the linter configuration files at the root of each repository for details about which checks are enabled.

Note that a few linters only run in CI via GitHub Actions and are not available in the standard development environment.

Unit Tests

To run Go unit tests:

make unit


To build the Go binaries provided by a repository:

make build

To package those Go binaries into container images:

make images

Note that Submariner will automatically rebuild binaries and images when they have been modified and are required by tests.

To prune all Submariner-provided images, ensuring they will be rebuilt or pulled the next time they’re required:

make prune-images

End-to-End Tests

To run functional end-to-end tests with a full multi-cluster deployment:

make e2e

Different types of deployments can be configured with using flags:

make e2e using=helm,globalnet

See Shipyard’s for the currently-supported using flags.

A subset of tests can be selected with Ginkgo focus flags:

make e2e focus=dataplane

To create a multi-cluster deployment and install Submariner but not run tests:

make deploy

To create a multi-cluster deployment without Submariner:

make clusters

To clean up a multi-cluster deployment from one of the previous commands:

make clean-clusters

Shell Session in Development Environment

To jump into a shell in Submariner’s standard development environment:

make shell