Releases: skupperproject/skupper
0.8.2
0.8.1
0.8.0
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
0.5.3
0.5.2
0.5.1
- Fix secret mounted for headless service proxies
- Don't create Routes on OpenShift for edge sites
- Fix Route for router console on OpenShift
- Allow console ingress to be specified separately
- Verification of ingress values
- Ensure skupper selector does not get corrupted when annotated service definition is reapplied
- Propagate annotations from skupper-site configmap to router and service-controller pods
- Configuration of internal router options (max hello age and session window controls)
0.5.0
This release introduces revised command line options for the skupper tool. The old options are still accepted but should be considered deprecated (they will give a message indicating the new form for the previous invocations).
StatefulSets and DaemonSets can now be annotated and will be exposed via skupper (previously this only applied to Deployments).
This also introduces an update subcommand, with which an existing site can be updated to a newer version. The update will also work with the site controller, however as this release requires read access for Daemonsets, the role the site c
ontroller runs under must also be updated. Using the sample yaml in the repo should correctly update a site[1].
[1] https://raw.githubusercontent.com/skupperproject/skupper/0.5/cmd/site-controller/deploy-watch-all-ns.yaml or https://raw.githubusercontent.com/skupperproject/skupper/0.5/cmd/site-controller/deploy-watch-current-ns.yaml