liquidmetal-dev / liquidmetal-dev/cluster-api-provider-microvm

Helm Chart for installing CAPMVM controller

Open
#259 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted kind/feature
Dominant language
Go
Stars
157
Forks
21
PR merge metrics
No merged PRs in 30d

Description

Currently the only supported way to install is via `clusterctl` (which uses the yamls uploaded to the release).

This makes it tricky if operators want to change values (such as resource limits). It also means that the provider cannot be installed via gitops.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the clusterctl installation YAMLs uploaded with releases and how the provider is currently packaged. Define the Helm chart values needed for operators to change settings such as resource limits, and verify that installation works through a GitOps workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.