0.11.0-m2

Advancing 0.11.0-m2 release to status: released

Signed-off-by: Mike Kolesnik <[email protected]>

0.10.1

• Inter-connecting clusters with overlapping CIDRs (Globalnet):
  • The initial Globanet implementation is deprecated in favor of a new implementation which is more performant and scalable.
    Globalnet now allows users to explicitly request global IPs at the cluster level, for specific namespaces, or for specific
    Pods. The new Globalnet implementation is not backward-compatible with the initial Globalnet solution and there is no
    upgrade path.
  • Globalnet now supports headless Services.
  • The default globalnetCIDR range is changed from 169.254.0.0/16 to 242.0.0.0/8 and each cluster is allocated 64K Global IPs.
  • Globalnet no longer annotates Pods and Services with global IPs but stores this information in ClusterGlobalEgressIP,
    GlobalEgressIP, and GlobalIngressIP resources.
• A new experimental load balancer mode was introduced which is designed to simplify the deployment of Submariner in cloud
  environments where worker nodes do not have access to a dedicated public IP. In this mode, the Submariner Operator creates a
  LoadBalancer Service that exposes both the encapsulation dataplane port as well as the NAT-T discovery port. This mode can be
  enabled by using subctl join --load-balancer.
• Submariner now supports inter-cluster connections based on the VXLAN protocol. This is useful in cases where encryption,
  such as with IPsec or WireGuard, is not desired, for example on connections that are already encrypted where the overhead
  of double encryption is not necessary or performant. This can be enabled by setting the --cable-driver vxlan option
  during subctl join.
• Submariner now supports SRV DNS queries for both ClusterIP and Headless Services. This facilitates Service discovery using
  port name and protocol. For a ClusterIP Service, this resolves to the port number and the domain name. For a Headless Service,
  the name resolves to multiple answers, one for each Pod backing the Service.
• Improved the Submariner integration with the Calico CNI.
• subctl benchmark latency and subctl benchmark throughput now take a new flag --kubecontexts as input instead of
  two kubeconfig files.

0.10.0-rc1

Advancing 0.10.0-rc1 release to status: released

Signed-off-by: Daniel Farrell <[email protected]>

0.10.0-rc0

v0.10.0-rc0 release, phase: released

Signed-off-by: Steve Mattar <[email protected]>

0.9.1

• The --kubecontext flag in subctl commands now works properly.
• Simplified subctl cloud prepare aws to extract the credentials, infrastructure ID, and region from a local configuration file (if available).
• The natt-discovery-port and udp-port options can now be set via node annotations.

0.10.0-m2

Start 0.10.0-m2 released release phase (#162)

Signed-off-by: Daniel Farrell <[email protected]>

0.10.0-m1

Release phase for v0.10.0-m1

Signed-off-by: Tom Pantelis <[email protected]>

0.9.0

• The gateway Pod has been renamed from submariner to submariner-gateway.
• The Helm charts now use Submariner's Operator to deploy and manage Submariner.
• Broker creation is now managed by the Operator instead of subctl.
• Each Submariner Pod now has its own service account with appropriate privileges.
• The Lighthouse CoreDNS server metrics are now exposed.
• The submariner_connections metric is renamed to submariner_requested_connections.
• The service-discovery flag of subctl deploy-broker has been deprecated in favor of the components flag.
• For cases in which cross-cluster connectivity is provided without Submariner, subctl can now just deploy
  Service Discovery.
• Improved Service CIDR discovery for K3s deployments.
• All Submariner Prometheus metrics are now prefixed with submariner_.
• With Globalnet deployments, Global IPs are now assigned to exported Services only. Previously, Globalnet annotated
  every Service in the cluster, whether or not it was exported.
• The name of the CoreDNS custom ConfigMap for service discovery can now be specified on subctl join.
• The strongswan cable driver that was deprecated in the v0.8.0 release is now removed.
• The Lighthouse-specific API is now removed in favor of Kubernetes Multicluster Services API.
• A new tool, subctl diagnose, was added that detects issues with the
  Submariner deployment that may prevent it from working properly.
• subctl commands now check if the subctl version is compatible with the deployed Submariner version.
• New flags, repository and version, were added to the subctl deploy-broker command.
• New Lighthouse metrics were added that track the number of services imported from and exported to other clusters.
• subctl show connections now also shows average rtt values.
• A new tool, subctl gather, was added that collects various information
  from clusters to aid in troubleshooting a Submariner deployment.
• Each gateway can now use a different port for IPsec/WireGuard communication via the gateway.submariner.io/udp-port node label.
• Gateways now implement a NAT-Traversal (NAT-T) discovery protocol that can be enabled via the gateway.submariner.io/natt-discovery-port
  node label.
• A cluster can now be configured in IPsec server mode via the preferred-server flag on subctl join.

0.9.0-rc0

submariner-io/submariner-website#457

0.9.0-m2

submariner-io/submariner-website#457