Geen omschrijving

Alexandre Alves 5dc2808170 Delete extensions/kamaji/0.2.0 directory 9 maanden geleden
.github 1893985fb2 removing yq dependency 1 jaar geleden
assets 7e7434e854 Delete assets/kamaji/kamaji-0.2.0.tgz 9 maanden geleden
charts 7b851b84d8 Delete charts/kamaji/0.2.0 directory 9 maanden geleden
extensions 5dc2808170 Delete extensions/kamaji/0.2.0 directory 9 maanden geleden
icons 9d6971ede0 CI Build Artifacts 9 maanden geleden
scripts 9beaa714f7 Merge branch 'main' into main 1 jaar geleden
LICENSE 3cec2fb5b5 Initial commit 2 jaren geleden
README.md 4dd744d70e update README 1 jaar geleden
index.yaml c66e8e956b CI Build Artifacts 9 maanden geleden
manifest.json 5bdd91ce07 Update manifest.json 9 maanden geleden

README.md

Partner Extensions

This repository is reserved for Rancher Extensions created by Rancher Partners. Extensions were introduced with Rancher 2.7.0.

The "Tested & Certified -- Rancher Extension" certification is part of the SUSE "Tested & Certified" product certification framework and it aims to address the growing need for a standardized, high-quality, and reliable ecosystem of Rancher Extensions that augment the capabilities of the Rancher by SUSE platform.

Requirements

  • Charts must be Helm 3 compatible.

  • Chart must be published in a public Github repository that we can reference.

Workflow

1. Fork the Partner Extensions repository, clone your fork, checkout the main branch and pull the latest changes.

Then create a new branch off of main

2. Update the manifest.json with your Extension metadata.

{
  "extensions": {
    "kubewarden": {
      "repo": "kubewarden/ui",
      "branch": "gh-pages",
      "versions": [
        "1.0.0",
        "1.1.0"
      ]
    }
  }
}

3. Commit your changes

git add manifest.json
git commit -m "Submitting kubewarden/ui version 1.1.0"

4. Push your commit

git push origin <your_branch>

5. Open a pull request on the main branch

Once your pull request is approved and merged, an automated workflow will sync this repository with the build assets from the supplied repository within the manifest.json file. When fully synced, a new release will be created and added to the releases section.

Configuration File

Required properties for manifest.json | Variable | Description | | ------------- |------------- | | [extension key] | This name is representative of the Extension package name. For example, the clock package within the ui-plugin-examples repository, clock would be the extension key. | repo | Defines the upstream Github repository to pull the build assets from. | branch | Defines which branch to pull from the upstream repo | versions | An array of version strings which correspond to the Extension package version(s) to be synced with this repository. For example, the clock extension package has two versions, 0.1.0 and 0.2.0 would be added.

Examples

{
  "extensions": {
    "kamaji": {
      "repo": "clastix/rancher-extension-clastix",
      "branch": "gh-pages",
      "versions": [
        "0.1.2"
      ]
    },
    "elemental": {
      "repo": "rancher/elemental-ui",
      "branch": "main",
      "versions": [
        "1.2.0",
        "1.1.0",
        "1.0.0"
      ]
    },
    "kubewarden": {
      "repo": "kubewarden/ui",
      "branch": "gh-pages",
      "versions": [
        "1.0.0",
        "1.0.1",
        "1.0.2",
        "1.0.3",
        "1.0.4",
        "1.0.5",
        "1.0.6",
        "1.1.0"
      ]
    }
  }
}