Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

A catalog based on applications from independent software vendors (ISVs). Most of them are SUSE Partners.

NotificationsYou must be signed in to change notification settings

rancher/partner-charts

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

The Rancher Partner Charts Repository is a collection of helm charts fromSUSE partners that are certified to run on Rancher-supported Kubernetesdistributions. Users can deploy these charts directly from the Apps view inRancher Manager. Minor Rancher-specific modifications are added to these chartsin order to provide the best possible experience using them from within Rancher.

partner-charts-ci is used toautomate many aspects of this repository. For the technical details of thisrepository, please consult thepartner-charts-ci documentation.

What are the requirements for adding a project to this repository?

Before submitting a chart to this repository, you must become aSUSE "Ready" Verified partner.You can start this process with aPartner Application.

To certify your software as SUSE "Ready", you need to attest that the software:

  • has been tested on RKE2 or K3s and publishes documentation showing supportedversions, including
    • version of Rancher (e.g. 2.8)
    • Rancher-supported distribution of Kubernetes (RKE2, K3s, EKS, etc.)
    • version of Kubernetes (e.g. 1.27)
  • is supported by your organization on the declared Rancher versions and configurations
  • is actively maintained and proactively updated
    • critical vulnerabilities are patched in a timely way
    • release notes disclose serious bugs and vulnerabilities
  • has a license and/or terms and conditions for use available in publicdocumentation or via the chart itself
  • does not compete commercially with Rancher Prime

Once your software is certified as SUSE "Ready", there are a few more requirementsfor inclusion in this repository. Your software's helm chart must:

  • be helm 3 compatible
  • be available from a publichelm repository(recommended) or a public git repository
  • havekubeVersion set in the chart's metadata
  • contain anapp-readme.md file (refer to thepartner-charts-ci documentation for more details)
  • be deployable from the current version of Rancher with the default values

Meeting these requirements ensures that Rancher users can easily deploy yoursoftware.

Note

This repository is not intended for certain kinds of software. For example:

  • slightly modified software or helm charts that meet the needs of only afew people
  • software maintained by an open source community without any backingorganization with which SUSE can have a partnership

How do I add my project to this repository?

In order to add a helm chart to this repository:

  1. Fork this repository.
  2. Follow the process for adding a package as described in thepartner-charts-ci documentation.partner-charts-ci can be obtained by runningscripts/pull-scripts, whichdownloads the right version for your machine tobin/partner-charts-ci.
  3. Create a pull request for your changes targeting themain-source branch inthis repository.Please ensure that your pull request only contains changesrelated to the package that you are adding. ThePACKAGE environment variableis useful for this; for more information please see thepartner-charts-ci documentation.

Who is responsible for maintaining the helm charts in this repository?

Each SUSE partner organzation is responsible for maintaining the versionsof their helm charts in this repository. However, SUSE also monitors thisrepository and may make changes if necessary.

When and how are helm charts removed from this repository?

Charts may be removed from this repository for a number of reasons:

  • Technical requirements are not met
  • A serious security problem is discovered
  • The vendor's SUSE "Ready" partnership is no longer active

In these cases, the chart will first be deprecated. While a chart is deprecated,no new versions of the chart will be added to this repository. The chart willbe left in the deprecated state for a minimum of 3 months, and then it will beremoved. The pull requests that deprecate and remove the chart will indicate analternative source (e.g. the corresponding upstream project orRancher PrimeApplication Collection) if one is available.


[8]ページ先頭

©2009-2025 Movatter.jp