R3.0 Release Notes

ISO image

You can find a pre-built ISO and Docker images for StarlingX release 3.0 at CENGN’s StarlingX mirror.

Branch

The source code for StarlingX release 3.0 is available in the r/stx.3.0 branch in the StarlingX Git repositories.

Deployment

A system install is required to deploy the StarlingX release 3.0. There is no upgrade path from previous StarlingX releases.

New features and enhancements

The list below provides a detailed list of features with the associated StoryBoard entries for the features.

  • Infrastructure and Cluster Monitoring

    2005733

  • Integrate with Openstack Train

    2006544

  • Integrate Distributed Cloud with containers

    2004766

  • Integrate Backup & Restore with containers

    2004761

  • Intel FPGA K8s Device Plugin Initial Integration

    2006495

  • Intel GPU K8s Device Plugin Integration

    2005937

  • Intel QAT K8s Device Plugin Integration

    2005514

  • Layered Build Prep

    2006166

  • Redfish Integration

    2005861

  • Support for authenticated registry for bootstrap and application apply

    2006274

  • Support for OpenID connet authentication parameters for bootstrap

    2006235

  • Support for floating and pinned workloads on worker nodes

    2006565

  • Support for NTP and PTP co-existence

    2006499

  • Time Sensitive Networking for VMs

    2005516

  • Upversion container components

    2005860,

    2006347

Known limitations in R3.0

The following are known limitations in the StarlingX R3.0 release. Workarounds are suggested where applicable. Note that these limitations are considered temporary and will likely be resolved in a future release.

Changing Keystone admin password

After the Keystone admin password is changed, kube-system namespace registry secrets must be manually updated. Tracking Launchpad: https://bugs.launchpad.net/starlingx/+bug/1853017

It is recommended that the Keystone admin password not be changed unless necessary.

Workaround: If you must update the WRCP’s Keystone admin user password in R3.0, you must also manually update the kube-system namespace’s registry secrets that hold the admin password for image pulls:

  1. Update the WRCP Keystone admin user password:

    openstack user set --password newP@ssw0rd admin
    
  2. Update the kube-system namespace’s registry-local-secret secret:

    kubectl -n kube-system create secret docker-registry registry-local-secret --docker-server=registry.local:9001 --docker-username=admin --docker-password=newP@ssw0rd -o yaml --dry-run=true > registry-local-secret-update.yaml
    kubectl -n kube-system replace secret registry-local-secret -f registry-local-secret-update.yaml
    
  3. Update the kube-system namespace’s default-registry-key secret:

    kubectl -n kube-system create secret docker-registry default-registry-key --docker-server=registry.local:9001 --docker-username=admin --docker-password=newP@ssw0rd -o yaml --dry-run=true > default-registry-key-update.yaml
    kubectl -n kube-system replace secret default-registry-key -f default-registry-key-update.yaml
    

In a distributed cloud deployment, the registry secrets must also be updated on all subclouds in the system.