submariner-io/submariner-operator

Operator that deploys the various Submariner components.

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

submariner-io/submariner-operator has 100+ stars and 70+ forks on GitHub, is written in Go, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 21 minutes ago
Added to GitGenius on October 15th, 2026
Created on October 4th, 2019
Open Issues & Pull Requests: 6 (+0)
GitHub issues: Enabled
Number of forks: 77
Total Stargazers: 125 (+0)
Total Subscribers: 11 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 29.5 hours
Mean response time: 43.9 days
90th percentile: 139.0 days
Tracked items: 21

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,172 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 3

Top labels

  • bug (9)
  • enhancement (9)
  • priority:low (5)
  • confirmed (4)
  • help wanted (4)
  • stale (4)
  • priority:high (3)
  • needs-triage (2)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Submariner Operator is a Kubernetes operator that deploys the various Submariner components onto a cluster.

The operator addresses the challenge of installing and managing Submariner, a system for connecting multiple Kubernetes clusters. Rather than requiring manual configuration of each component, the operator automates deployment through Kubernetes-native custom resources, allowing users to define their desired Submariner configuration declaratively and have the operator handle the underlying setup.

The tool suits teams running multiple Kubernetes clusters who need to establish secure connectivity between them. It works across different Kubernetes distributions and cloud platforms, with quickstart guides available for sandbox environments using kind, OpenShift on AWS, Google Kubernetes Engine, Rancher, and hybrid cloud setups combining AWS with vSphere. The operator is registered on OperatorHub, making it discoverable and installable through standard Kubernetes package management workflows.

The project maintains active testing infrastructure including periodic validation runs and flake detection to catch intermittent failures. The team follows established security practices as recognized by the Core Infrastructure Initiative Best Practices program. Release workflows are automated to ensure consistent image builds and deployment artifacts.