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

We are using CAPMVM through WGE and can not create clusters that have '-' in the name

Open
#145 1 comment 0 reactions 0 assignees View on GitHub
kind/bug
Dominant language
Go
Stars
157
Forks
21
PR merge metrics
No merged PRs in 30d

Description

**What happened:**
[A clear and concise description of what the bug is.]
An request to create a cluster wtih '-' in the name like 'paul-mvm-36' will fail. The initial control plane machine gets deployed, but I can never reach the kubernetes api-server.

**What did you expect to happen:**
Provisioning should work and it should not matter if we have a '-' in the cluster name or not.

**How to reproduce it:**
Go to [the demo environment](http://demo.weavegitops.com) and deploy a cluster. Follow the instructions [in this doc](https://docs.google.com/document/d/1WHo_9xgLtvc6pL1OGNTZ5MwdJqBvT7QbAfDuZI_v_BE/edit#)

**Environment:**

- capmvm version:0.4.0

Contributor guide

Open the contributing guide

Research direction

Reproduce the failure by deploying a cluster named `paul-mvm-36` in the linked demo environment, following the referenced instructions. Trace why the control plane starts but the Kubernetes API server remains unreachable when the name contains `-`; done means provisioning succeeds for hyphenated cluster names as well as names without hyphens.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
infrastructure
Issue type
Bug
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.