v0.5.0-rc1

Note: this is a release candidate. The final release will ship once we identify and address any blocker bugs found by the community.

To run this RC (or any non-final release) of Rio, you just need to specify the version during installation:

 curl -sfL https://get.rio.io | INSTALL_RIO_VERSION=v0.5.0-rc1 sh -

Features and Enhancements

• Service Mesh Interface support - Rio now leverages Service Mesh Interface (SMI) to support different service mesh backends. This gives you more power and control over your tech stack. We've also made Linkerd the default SMI backend. This will reduce Rio's overall footprint in your underlying Kubernetes cluster. You can use Istio by running rio install --mesh-mode istio.
• Improved Continuous Delivery workflows with GitHub - Rio now integrates with GitHub's Deployment API to improve your CD workflows. This means that when you use Rio's Continuous Delivery feature, you will be able to check your app's status, view build logs, and even access your app directly from the GitHub Pull Requests and Deployments pages. #406
• Istio upgraded - We've upgraded the version of Istio that Rio deploys and uses to 1.2.5.

Bug fixes and minor enhancements

• Added the ability to configure build timeouts #418
• Added the ability to see log timestamps when using rio logs #421
• Fixed a bug that caused long-running builds to timeout. You can now configure the build timeout #418
• Fixed a bug that Rio subcommand will not show help message if rio is not installed in the current cluster #491
• Fixed a bug that Public domain will not provision letsencrypt certificates if pointing to services or routers #444 #481
• Fixed a bug that config and secret will not be shown correctly in edit #425
• Fixed a bug that rio revision -q will panic #413

Important

Rio is currently in Alpha. This means that APIs and major pieces of functionality can change significantly between releases. Additionally, upgrading Rio is not thoroughly tested. You should be aware of the following changes in this release:

• The SMI and Linkerd implementations are likely to cause upgrade issues. The safest path forward is to uninstall Rio and then re-install.
• We've dropped support for the ingress gateway mode installation option. This was introduced and made the default gateway mode in v0.4.0, but we've removed it because it is incompatible with how Envoy proxy handles the x-forwarded-proto header. The default mode is now Service loadblancer (svclb) on ports 9080 and 9443.