Rancher - Tech Preview Update 3/26/2018

Announcements
1

Release v2.0.0-alpha23

Please view the latest Rancher 2.0 Project Plan for the most current feature list and schedule.

Helpful Links

Quick Start Guide
Forums for feedback/comments/suggestions
User Slack#2-0-tech-preview

Important

For the purpose of the tech preview, we will always update rancher/server:preview with the latest preview builds until we GA. After we GA, we will update the appropriate latest and stable tags as required.

Versions

  • rancher/server:v2.0.0-alpha23
  • rancher/agent:v2.0.0-alpha23

Change in Accessing the UI

Previously Rancher’s UI was exposed on port 8080, but with the new changes, the docker run command has been updated to:

docker run -d -p 80:80 -p 443:443 rancher/server:preview

You can access the UI at https://<server_ip>.

New Features

NOTE: Please bear in mind that, with this preview release, not all features are ready for consumption.
You might find some features disabled in the UI. We will quickly provide upcoming builds as 
they become available.  The following are some of the highlighted features for this preview build.  More details can be found in the [Rancher 2.0 Project Plan](https://github.com/rancher/rancher/wiki/Rancher-2.0)
  • Project based network policy enabled - Starting with this build, Rancher will only allow inter-project communication between namespaces. Intra-project communication is only achieve by publishing your service. This is only supported if you create a non-GKE/AKS cluster with the canal network driver enabled (this is the default option).
  • ActiveDirectory-as-an-AuthProvider - ActiveDirectory is now an option as an authprovider in addition to GitHub.
  • Volume support for Workloads - PersistentVolumes (PV), StorageClasses, and PersistentVolumeClaims (PVC) are now enabled as part of the UI.
    • Secrets management should now work.
  • Kubectl Shell - kubectl shell is now available per cluster.

Upcoming Milestone Release Features

The following features should be on the next upcoming milestone (subject to change):

  • SAML-as-an-AuthProvider
  • PodSecurityPolicies enabled
  • Directory based logging - Rancher bind mounts in a volume to support collecting logs that are written to a directory vs stdout/err

Known Major Issues

Rancher CLI Downloads