openSUSE:Slowroll:Build:2

https://en.opensuse.org/openSUSE:Slowroll area for building and openQA testing https://download.opensuse.org/repositories/openSUSE:/Slowroll:/Build:/2/standard/ openSUSE:Slowroll

Slowroll

https://en.opensuse.org/openSUSE:Slowroll = a derivative codestream of openSUSE:Factory that uses automated rules to limit the rate of change to the codebase Release manager: bmwiedemann https://www.zq1.de/~bernhard/linux/opensuse/slowroll/slowroll-vs-tumbleweed-updates.svg https://download.opensuse.org/update/slowroll/repo/oss/ openSUSE:Slowroll:Base:2

staging area for new Base snapshot from Tumbleweed

Before a version bump, I collect i586 and bootstrap binaries here. These are missing in released Tumbleweed snapshots, but are needed for building packages. Also binaries required for DVD builds, because product-builder cannot use those from download-on-demand (dod) https://download.opensuse.org/repositories/openSUSE:/Slowroll:/Base:/2/standard/ openSUSE:Tumbleweed

Tumbleweed

Tumbleweed is the openSUSE Rolling Release This OBS Project represents the content of the currently published snapshot. The newer repository for next publish can be found in openSUSE:Factory standard repository. https://download.opensuse.org/repositories/openSUSE:/Tumbleweed/slowroll-next/ clusterctl

CLI tool to handle the lifecycle of a Cluster API management cluster

The clusterctl CLI tool handles the lifecycle of a Cluster API management cluster. The clusterctl command line interface is specifically designed for providing a simple “day 1 experience” and a quick start with Cluster API. It automates fetching the YAML files defining provider components and installing them. Additionally it encodes a set of best practices in managing providers, that helps the user in avoiding mis-configurations or in managing day 2 operations such as upgrades. Below you can find a list of main clusterctl commands: * clusterctl init: Initialize a management cluster. * clusterctl upgrade plan: Provide a list of recommended target versions for upgrading Cluster API providers in a management cluster. * clusterctl upgrade apply: Apply new versions of Cluster API core and providers in a management cluster. * clusterctl delete: Delete one or more providers from the management cluster. * clusterctl generate: cluster Generate templates for creating workload clusters. * clusterctl generate yaml: Process yaml using clusterctl’s yaml processor. * clusterctl get kubeconfig: Gets the kubeconfig file for accessing a workload cluster. * clusterctl move: Move Cluster API objects and all their dependencies between management clusters. * clusterctl alpha rollout: Manages the rollout of Cluster API resources. For example: MachineDeployments. Avoiding GitHub rate limiting While using providers hosted on GitHub, clusterctl is calling GitHub API which are rate limited; for normal usage free tier is enough but when using clusterctl extensively users might hit the rate limit. To avoid rate limiting for the public repos set the GITHUB_TOKEN environment variable. To generate a token follow this documentation. The token only needs repo scope for clusterctl.