Last Update: 2018-06-26

Table of Contents

Technical Details
What’s New with Beta SUSE CaaS Platform 3?
Planned Releases
In Depth
Report Issues
Mailing list
Frequently Asked Questions
Why are there 3 ISOs available per product?
Error message when trying to download isos
Beta Test Subscription and Registration Code
Private channel for sensitive data
Contact Beta Manager


SUSE CaaS (Container as a Service) Platform is an application development and hosting platform for container applications and services that enables you to provision, manage, and scale container-based applications and services.

SUSE CaaS Platform consists of 3 key components

  • Orchestration:
    SUSE CaaS Platform uses open source Kubernetes to provide production grade container orchestration at scale.
  • OS for Microservices & Containers:
    At the heart of SUSE CaaS Platform is the microservices and containers host OS – SUSE MicroOS.
  • Configuration:
    SUSE CaaS Platform uses open source Salt to automate the cluster at scale. Using Salt you can achieve a complete and automatic installation and configuration of components. Additionally, you can automate using cloud-init to pass configuration data to systems.


Technical details:

  • Ready to run out of the box: Not just a Bash login prompt where you need to configure everything
  • Btrfs with snapshots and rollback for transactional updates
  • Read-only file system with OverlayFS for /etc
  • cloud-init for initial configuration (Network, Accounts, Salt)
  • Salt for full system configuration
  • Administration node with dashboard to manage cluster
  • Kubernetes 1.9

SUSE MicroOS comes with a novel file system configuration based on Btrfs and OverlayFS:

  • SUSE MicroOS is based on SUSE Linux Enterprise Server 12 SP3
  • The base OS and snapshots are read-only
  • Subvolumes for data storage are read-write
  • OverlayFS is used for /etc (for cloud-init and Salt)

To manage SUSE MicroOS deployments, cloud-init is used:

  • Very flexible and already well-known by administrators in the cloud environment
  • cloud-init has been enhanced to be able to configure Zypp repositories and read configuration from local directories

What’s New with Beta SUSE CaaS Platform 3?

SUSE CaaS Platform 3 Beta delivers on SUSE’s commitment to rapidly advance the platform, adding powerful tools to simplify large scale application deployment, incorporating an updated release of Kubernetes, a disconnected registry for offline deployments, and a smooth integration with other SUSE Products (e.g. SUSE OpenStack Cloud)

Users of SUSE CaaS Platform 3 will enjoy these new benefits:

  • Ability to run offline deployments with a proxy registry
  • Enhanced performance, extensibility, and hardware support with Kubernetes 1.9 and SUSE MicroOS updates
  • Enhanced debugging tools delivered via a new Toolchain module for SUSE CaaS Platform with a registered system
  • There is now an option in Velum to retry failed orchestrations
  • We enabled Node removal on a bootstrapped cluster in our dashboard Velum


Planned Releases

Beta 1May 7, 2018
Beta 2May 18, 2018
RC1June 6, 2018
First Customer ShipmentEnd of June 2018



Please note that we reserve the right to change or adapt this schedule depending on various factors. Rest assured that we will communicate if there is any change of plan.



SUSE Container as a Service Platform 3 Release Candidate 1

We are offering the following image on x86_64 only:

  • DVD ISOs,
  • XEN and KVM qcow2 images,
  • Hyper-V image,
  • VMware image,
  • Openstack image




Note: The following Documentations are drafts.

And will remain as such through out the SUSE CaaS Platform Beta Program. Documentations for Beta Products do not yet have the quality, accuracy and content of our official documentations. However we will update these documentations on the fly during the SUSE CaaS Platform Beta Program.


Release Notes for SUSE CaaS Platform 3 Beta:

Fixed in RC 1:

  • (bsc#1090067) CaaSP CPI does now work on OpenStack with self-signed CA,
  • (bsc#1080978 Enhanced stability during upgrade from CaaSP 2,
  • (bsc#1087447) A space entered before fqdn of the master in UI caused orchestration to fail,
  • and other performance and UI enhancements.


  • DHCP:

Your DHCP server should provide resolvable hostnames. If this is not the case like with libvirt/KVM, you should consider providing one yourself by appending this kernel parameter "hostname=HOSTNAME" during installation.
However, the kubeconfig file downloaded from the Dashboard could contain an incorrect “server” hostname that should be replaced with the IP address of your Master.
For more information read:

  • Autoyast/VMX-Images:

If you install via autoyast or one of the provided VMX beta images (KVM,Xen,VMware,…) please set a password or SSH key via cloud-init to be able to login.


In Depth

Available on the Product Media:

  • Read the READMEs on the media.
  • Get the detailed change log information about a particular package from the RPM (where <FILENAME>.rpm is the name of the RPM):
    rpm --changelog -qp <FILENAME>.rpm
  • Check the ChangeLog file in the top level of the media for a chronological log of all changes made to the updated packages.

Online Documentation:



Whenever you find a bug or your are scratching you head on using SUSE CaaS Platform, we highly recommend to seek for help on our mailing list first, then if it really make sense you should open a bug report.

Mailing List is our dedicated Mailing List to discuss around the SUSE CaaS Platform Beta product. It is used by the SUSE Release Team to announce new beta images and technical information, as well as for general or technical questions, feedback, or defect reports related to SUSE CaaS Platform Beta products from our beta testers base.

Only subscribers can post to our mailing lists. To subscribe, please go to

To see the collection of prior postings to the list, visit the caasp-beta Archives.

Please refer to our Mailing Lists Guideline for more information.


Here are the links to the SUSE CaaS Platform Bugzilla product that you will use for reporting the defects of the following products:

Please refer to our complete Bugzilla guideline for more information and before creating your first bug report: how to use Bugzilla

Frequently Asked Questions
    • Why are there 3 ISOs available per product?

      We offer 3 DVD ISOs:

      • SUSE-CaaS-Platform-3.0-DVD-x86_64-BetaX-DVD1.iso = DVD1 contains the binaries
      • SUSE-CaaS-Platform-3.0-DVD-x86_64-BetaX-DVD2.iso = DVD2 the sources
      • SUSE-CaaS-Platform-3.0-DVD-x86_64-BetaX-DVD3.iso = DVD3 the debuginfo packages

      The final product will not contain the debuginfo packages on the media.

      For installation purposes you just need DVD 1 for your architecture. Please verify the sha256sum of the ISO using the SHA256SUMS file, which can also be found on the download page.


– Error message when trying to download isos

Well, sorry for the inconvenience, please report your issue to:
One quick workaround would be to remove and cookies from you browser and try again.

  • Beta Test Subscription and Registration Code



    Regular product subscription and registration code will not work with the beta products!

    Thus we will not provide a beta product subscription or beta product registration code by default for the SUSE CaaS Platform Beta Program. You should request one via, but we reserve the right to review your case and eventually provide one for your personal beta test.

    Without a beta registration code for SUSE CaaS Platform 3 you won’t be able to access the online channels.

  • Private channel for sensitive data

    In case you are a SUSE’s partners or customers and would like to share some sensitive data with us for multiple reasons (data for bug reports, feedbacks, etc).
    Please contact us at, and we will review your case and help you have a private channel with us.

  • Contact Beta Manager

    For questions related to the beta test infrastructure, for example download issues or problems with reporting bugs or the mailing list, please write to