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

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

  • Comments

    • hfschmidt
      about 2 months 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

    Zero Trust vSphere Provisioning from Rancher by wjimenez

    Currently, when Rancher tries to provision a Ku...


    Near-zero downtime upgrades for stateful services with Rancher by mlnoga

    Project Description

    Containers are great ...


    Rancher and cf-on-k8s by mgrifalconi

    Project Description

    Cloud Foundry For Kuber...


    Rancher & Gardener: Stronger Together by mlnoga

    Project Description

    Gardener is SAP's por...


    Uyuni/SUSE Manager containerization project by moio

    Deploy Uyuni as an **app from the Rancher marke...