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

0.8.4

Fix panic when site controller checks exiting site

0.8.3

Ensures ingress or httpproxy resources are created in the correct namespace.
Does not create console ingress or httpproxy if console is not enabled.
Sample yaml for deploying site controller adds permission for creating network policy.

0.8.2

Fix for site controller updates for existing sites not in default namespace (#639)

0.8.1

Includes support for new ingress mode, contour-http-proxy.

0.8.0

Please note that this version of skupper is not compatible with previous versions due to the newly added support for exposing multiple ports on the same service. You must ensure that all connected sites are on this version.

0.7.0

This release includes the following new functionality:

• The ability to create off-cluster gateways, allowing services running outside kubernetes to be exposed to all skupper sites in an application network, and allowing services running within kubernetes to be accessed as well

• The introduction of token claims to reduce the risk of certificates being exposed. The claims can be restricted (by default they can only be used once and must be used within 15 minutes of being issued, but this is configurable through the skupper token create command. Claims are automatically exchanged for certificates avoiding the certificates ever needing to be stored outside the namespace using them. The default behaviour of skupper token create is to issue a restricted claim. The original behaviour can be obtained by using the --token-type cert option.

• Support for nodeports or nginx ingress (instead of openshift routes or loadbalancer services) (Note that tls passthrough must be enabled for nginx ingress controller for this option to work with skupper).

0.6.0

Update for 0.6.0