Skip to content

Edition d'un Muppy Package

Les Muppy Package ont la même structure que les Helm Packages. Ils sont composés des fichiers suivants:

  • chart.yml ; qui décrit le package
  • des config templates (Muppy gère différents type de config: Config, Jobs, CRON)
  • un fichier values.yml
  • divers fichiers (licence, readme,...)

Package Creation

To create a Muppy Package, the best is to fork an existing one, the closest to you needs and connect it to Muppy.

Muppy allows to fork a package on gitlab or github.

Muppy Official K8s Package Repository is https://gitlab.com/muppy-io/k8s-packages/.

  • Activate Developer Mode using the User menu
  • Create a new Muppy / K8s / K8s Packages
  • Select an App
  • Enter Muppy Package as Type
  • Enter GitLab Projectas Package Source
  • In tab Advanced enter:
  • GitLab Project ID from GitLab General project page
  • GitLab Token only for private repositories
  • GitLab Repo Branchif you don't want to use the default branch then click on [Connect]. Check GitLab State becomes connected
  • Then click on [Refresh Package from source] in the K8s Package form header.

You package is ready to used.

Package Update

Warning

Package update must be done in your Git repository only !

Commit your changes and when you want to update your package in Muppy:

  • click on [Refresh Package from source] in the K8s Package form header.

Package Form Reference

  • [Gitlab Connect] ; Call GitLab API to fetch project information then Refresh branch info
  • [Refresh branch info] ; Call Gitlab API to get latest branch info (commit and tags for GitLab Repo Branch).
  • [Refresh Package from Source] ; Call K8s Package's Load Archive Package then Extract Package Archive
  • [Load Archive Package] ; Download a package archive (from Package Archive URL) of the latest commit (Git Branch Commit) for GitLab Repo Branch.
  • [Extract Package Archive] ; Update current K8s Package form and data from Package Archive content.