0.6.1 release

No functional changes exist in this release, but fixes the testing
issue of Lighthouse + Globalnet handled in [1] and [2].

This version will also set imagePullPolicy of pods to Always when
the "devel" Cutting edge version is installed.

[1] submariner-io/lighthouse#272
[2] submariner-io/lighthouse#275

0.6.0 release

Bump Submariner & Lighthouse to 0.6.0

Signed-off-by: Miguel Angel Ajo <[email protected]>

0.5.0

This release mainly focused on continuing the alignment of Lighthouse's service discovery support with the [Kubernetes Multicluster
Services KEP][MCS KEP].

• Lighthouse has been modified per the [Kubernetes Multicluster Services KEP][MCS KEP] as follows:
• The MultiClusterService resource has been replaced by ServiceImport.
• The ServiceExport resource is now updated with status information as lifecycle events occur.
• Lighthouse now allows a ServiceExport resource to be created prior to the associated Service.
• Network discovery was moved from subctl to the Submariner operator.
• Several new commands were added to subctl: export service, show versions, show connections, show networks, show endpoints, and show gateways.
• The subctl info command has been removed in lieu of the new show networks command.
• The Globalnet configuration has been moved from the broker-info.subm file to a ConfigMap resource stored on the
  broker cluster. Therefore, the new subctl cannot be used on brownfield Globalnet deployments where this information
  was stored as part of broker-info.subm.
• subctl now supports joining multiple clusters in parallel without having to explicitly specify the globalnet-cidr for the
  cluster to work around this issue. The globalnet-cidr will automatically be allocated by subctl for each cluster.
• The separate --operator-image parameter has been removed from subctl join and the --repository and --version
  parameters are now used for all images.
• The Submariner operator status now includes Gateway information.
• Closed technical requirements for Submariner to become a CNFC project, including Developer Certificate of Origin compliance,
  and source code linting.

Libreswan cable driver, Kubernetes multicluster service discovery

This release is mainly focused on the libreswan Submariner cable driver implementation,
as well as standardizing the service discovery support in Lighthouse with the upstream kubernetes KEP [1].

• The libreswan IPsec cable driver is available for testing. It’s been included on the testing matrix of the project.
• Lighthouse has been modified per [1] as follows:
  • A ServiceExport object needs to be created alongside any Service that is intended to be exported to participant clusters
  • The supercluster services can now be accessed with ..svc.supercluster.local
• Globanet overlapping CIDR support improvements and bug fixes
• Multiple CI improvements implemented from shipyard
• The testing matrix is now run via GitHub actions
• The submariner-operator now completely handles the Lighthouse deployment via the ServiceDiscovery CRD.
• subctl verify is now available for connectivity, service-discovery and gateway-failover.

Fix verify-connectivity with globalnet

This release fixes subctl verify-connectivity when used with globalnet.

v0.3.0

• Lighthouse no longer depends KubeFed. All metadata exchange is handled over the Broker as MultiClusterService CRs.
• Experimental Wireguard support has been added as a pluggable CableDriver option in addition to the current default IPsec (note: still not compatible with globalnet)
• Submariner reports the active and passive gateways as well as connection status as a gateway.submariner.io CRD.
• The Submariner Operator reports a detailed status of the deployment.
• The gateway redundancy/failover tests are now enabled and stable in CI.
• Globalnet hostNetwork to remote globalIP is now supported. Previously, when a pod used hostNetworking it was unable to connect to a remote service via globalIP.
• A globalCIDR can be manually specified when joining a cluster with globalnet enabled. This enables CI speed optimizations via better parallelism.
• Operator and subctl are more robust via standard retries on updates.
• Subctl creates a new individual access token for every new joined cluster.

Overlapping CIDR support

• Support deployment Overlapping CIDRs between clusters (globalnet)

Submariner with some light +

• Fixed issue with wrong token stored in subm file #244
• Updated to submariner v0.1.1
• Added flag to disable the OpenShift CVO #235
• Fixed several service-discovery related bugs #194 , #167
• Fixed several panics on nil network discovery
• Now checks if the IPs for the cluster you're trying to join overlaps with an existing one.
• Fix context handling related to service-discovery / kubefed #180
• Use the right CoreDNS image for OpenShift.

Submariner with some light

This release includes several enhancements:

• a developer-evaluation support for lighthouse project (DNS discovery).
• this release has been synchronized with all other components as 0.1.0
• support to verify-connectivity between two connected clusters
• deployment of submariner gateways based in daemonsets instead of deployments
• renaming submariner pods to "submariner-gateway" pods for clarity
• print version details on crash (subctl)
• stop storing IPSEC key on broker during deploy-broker, now it's only contained into the .subm file
• version command for subctl
• nicer spinners during deployment (thanks to kind)

subctl usability release

This release introduces several changes to subctl:

• Various usability fixes
• Support for kubernetes >1.14
• Invert the broker setup to not deploy dataplane connectivity by default