Releases: submariner-io/releases
Releases · submariner-io/releases
0.19.0-rc2
Advancing 0.19.0-rc2 release to status: released Signed-off-by: Aswin Suryanarayanan <asuryana@redhat.com>
0.17.3
Advancing 0.17.3 release to status: released Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
0.18.1
0.19.0-rc1
Advancing 0.19.0-rc1 release to status: released Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
0.19.0-m3
Advancing 0.19.0-m3 release to status: released Signed-off-by: Maayan Friedman <maafried@redhat.com>
0.19.0-m2
Advancing 0.19.0-m2 release to status: released Signed-off-by: Daniel Farrell <dfarrell@redhat.com>
0.14.9
0.15.5
0.19.0-m1
Advancing 0.19.0-m1 release to status: released Signed-off-by: Maayan Friedman <maafried@redhat.com>
0.18.0
New features
subctl join
and other commands now support HTTP proxy arguments corresponding to the HTTP proxy environment variables
that are propagated to the various pods.subctl verify
now outputs a short description of each test that is run.
Other changes
- Fixed an issue in Service Discovery where un-exporting a Service on one cluster and then quickly exporting it on another cluster could
result in a missingServiceImport
resource and cause name resolution failures. - Reduced and restricted the RBAC permissions for the various Submariner components to only what is actually needed to reduce any
potential attack surface. - Improved the performance of Service Discovery exporting at scale which was hindered by excessive throttling delays when exporting many
services quickly. - To reduce RBAC permissions, Submariner no longer annotates Node resources. After upgrade, any
submariner.io/*
annotations will not be removed because Submariner no longer has Node update permission. - Health check counters on the Gateway resource now report correct information after a gateway leader re-election occurs.
- AWS cloud prepare now supports the resource naming convention implemented in Openshift 4.16 and above.