Skip to content

Make publishing plugins easier #2632

Open
@joaquimrocha

Description

@joaquimrocha

Is your feature request related to a problem? Please describe the impact that the lack of the feature requested is creating.

More and more people are asking for how to deploy Headlamp with plugins. This has been kind of a manual process, but for the Flux UI we do publish an OCI image.

We do have a Dockerfile for building a plugin OCI which makes it easy already, but we could make it easier by having a release process to make it easier.

Describe the solution you'd like

I would like to have:

  • A script to build both the OCI and the plugin tarball, so they would be ready to push to Github
  • A Github action (on headlamp-k8s/plugins) for manually releasing a plugin. This should:
    • Build the tarball
    • Build the OCI (if the ArtifactHub pkg file has the in-cluster tag)
    • Push the OCI to the registry
    • Push the tarball to a draft release (see the push-release-assets.js script in headlamp)
    • Update the ArtifactHub pkg file for that plugin

What users will benefit from this feature?

Us maintainers and anyone looking for creating their own plugin repo.

Are you able to implement this feature?

I prefer to delegate 😄

Metadata

Metadata

Assignees

Labels

infraInfrastructure / Build related issueskind/featureCategorizes issue or PR as related to a new feature.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.plugins

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions