1.2.0

• Added libpod library for podman implementation of the client interface
• New Skupper man command to generate man pages and markdown (hidden)
• Enabled TCP protocol to expose services over TLS using the certificates generated by Skupper (using --enable-tls option)
• Initialization improvements, so that Skupper doesn't fail if the route already exists
• Fixed bug related to the link format in the network status command
• Added annotations to adjust headless proxies
• Reduced aggressiveness of back-off error in config-sync container

Images icluded:

• quay.io/skupper/skupper-router:2.2.0
• quay.io/skupper/service-controller:1.2.0
• quay.io/skupper/config-sync:1.2.0
• quay.io/skupper/site-controller:1.2.0

1.1.1

Fixes bug where site-controller did not wait for LoadBalancer external address.

1.1.0

• Support for the following commands is removed:

  • skupper init --cluster-local: Use skupper init --ingress [loadbalancer|route|none] instead.
  • skupper init --edge: Use skupper init --router-mode [interior|edge] instead.
  • skupper bind: Use skupper service [bind|unbind] instead.
  • skupper unbind: Use skupper service [bind|unbind] instead.
  • skupper list-connectors: Use skupper link status instead.
  • skupper connect: Use skupper link [create|delete|status] instead.
  • skupper disconnect: Use skupper link [create|delete|status] instead.
  • skupper check-connection: Use skupper link [create|delete|status] instead.
  • skupper connection-token: Use skupper token create instead.
  • skupper list-exposed: Use skupper service status instead.

• The previous release changed skupper gateway commands considerably.
  This release drops support for older methods of using a gateway.
  See Using the Skupper CLI for the currently supported gateway commands.

• This release includes a skupper cli for MacOS on ARM

• The mapping flag is deprecated for the skupper service create command.
  Use the protocol flag instead.

1.0.2

Highlights:

• Fixes #785
  • Note: If the flow-collector container has already been deployed in an active skupper site, the skupper-update command will not regenerate the credentials in the current version; it will be needed to delete and re-init the site.

1.0.1

Highlights:

• Fixes to Gateway to properly detect and remove resources no longer in use
• Policy bug fixes and improvements
• Network command: requests to the service-controller will have a timeout. In case of timeout, the command will show local information

1.0.0

Skupper relies on a router to transport traffic across the VAN.
This release replaces the Apache Qpid Dispatch router with a fork of that router named Skupper router.
The development of Skupper router will focus on the Skupper use case.

WARNING: This release of Skupper is incompatible with all previous releases.
To avoid disruption, you must upgrade all sites in your VAN (service network) to this release as described below

Highlights:

• New skupper network status command to display overview of the skupper network.
• New policy system as described in Securing a service network
• TLS support for services using the HTTP2 protocol.
• The skupper router no longer restarts when creating a link.

This release of Skupper includes some Skupper Gateway changes. We recommend removing any gateways before upgrading, and recreating those gateways after a successful upgrade.

• Only one gateway per user/host. Previously, a user could create multiple gateways, this is no longer possible. If you require multiple gateways per host, create a new user for each gateway.
• When exposing a service using a gateway, the service type is not supported for this release, but will be available in future releases. To workaround this issue use a container:
  skupper gateway expose <address> <host> <port...> -type [docker|podman]

To upgrade a site to this release of Skupper:

$ skupper update

1.0.0-preview2

Skupper relies on a router to transport traffic across the VAN.
This release replaces the Apache Qpid Dispatch router with a fork of that router named Skupper router.
The development of Skupper router will focus on the Skupper use case.

WARNING: This release of Skupper is incompatible with all previous releases.
To avoid disruption, you must upgrade all sites in your VAN (service network) to this release as described below

Highlights:

• New skupper network status command to display overview of the skupper network.
• New policy system as described in Securing a service network
• TLS support for services using the HTTP2 protocol.
• The skupper router no longer restarts when creating a link.

This release of Skupper includes some Skupper Gateway changes. We recommend removing any gateways before upgrading, and recreating those gateways after a successful upgrade.

• Only one gateway per user/host. Previously, a user could create multiple gateways, this is no longer possible. If you require multiple gateways per host, create a new user for each gateway.
• When exposing a service using a gateway, the service type is not supported for this release, but will be available in future releases. To workaround this issue use a container:
  skupper gateway expose <address> <host> <port...> -type [docker|podman]

To upgrade a site to this release of Skupper:

$ skupper update

0.8.7

• Fix to upgrading from earlier versions, ensuring config-sync side car is added to router
• Fix in error handling for case where skupper-internal configmap does not exist

0.8.6

Fixes issue #671

0.8.5

Fixes issue #662