Project Description

Releasing rancher is currently a complex process and requires release captains to make alot of manual commits. Much of this work is very procedural. Our goal is to automate the more mundane tasks to make it faster and easier for new release captains to get started.

Goal for this Hackweek

To greatly simplify the rancher release process and automate a lot of the manual work that goes into releasing rancher.

Looking for hackers with the skills:

rancher releases

This project is part of:

Hack Week 20

Activity

  • almost 2 years ago: pgonin liked this project.
  • almost 2 years ago: jblainchristen liked this project.
  • almost 2 years ago: rsanna liked this project.
  • almost 2 years ago: rsanna joined this project.
  • almost 2 years ago: jpayne added keyword "rancher" to this project.
  • almost 2 years ago: jpayne added keyword "releases" to this project.
  • almost 2 years ago: jpayne joined this project.
  • almost 2 years ago: svansteenis started this project.
  • almost 2 years ago: jpayne originated this project.

  • Comments

    • hfschmidt
      almost 2 years ago by hfschmidt | Reply

      This is interesting! In SCC (scc.suse.com), customers will be able to open their support cases. So SCC will also need to keep track of Rancher / Longhorn versions, so that customers can select the correct version when they open their support case.

    Similar Projects

    Humidity sensors with dashboard by joachimwerner

    Build a network of ("edge") humidity sensors...


    Deploy Uyuni proxy using Elemental and Fleet by cbosdonnat

    Project Description

    Now that Uyuni proxy ...


    Rancher Token Revoker by mbolot

    [comment]: # (Please use the project descriptio...


    A CLI for Harvester by mohamed.belgaied

    [comment]: # Harvester does not officially come...


    Rancher Manager of Managers with KCP by rcase

    [comment]: # (Please use the project descriptio...