dsieradzki / makoon Goto Github PK

• Check IP availability in cluster creator
• Check IP availability in cluster management

• Support creating helm apps and workload templates.
• Support saving running apps and workloads as templates
• Creating template collections

Hi, my workflow as below

1. I wanted to add additional worker node.
2. I do not want extra master
3. I know my master add node key ( microk8s.addnode )
4. I am thinking of using k4prox to add additional workers node
5. delete all default master
6. click add worker node ( ERROR : Didn't expect it to auto add master node )

Getting this error while executing wails build:

go version go1.18.1 linux/amd64
Wails CLI v2.2.0

A Type: desktop
Platforms: linux/amd64
Compiler: /usr/bin/go
Skip Bindings: false
Build Mode: Production
Frontend Directory: /home/nico/Documents/k8/k4prox/frontend
Obfuscated: false
Skip Frontend: false
Compress: false
Package: true
Clean Bin Dir: false
LDFlags: ""
Tags: []
Race Detector: false

Building target: linux/amd64

• Generating bindings: Done.

• Installing frontend dependencies: Done.

• Compiling frontend:

  [email protected] build
  tsc && vite build

  file:///home/nico/Documents/k8/k4prox/frontend/node_modules/vite/bin/vite.js:7
  await import('source-map-support').then((r) => r.default.install())
  ^^^^^

  SyntaxError: Unexpected reserved word
  at Loader.moduleStrategy (internal/modules/esm/translators.js:133:18)
  at async link (internal/modules/esm/module_job.js:42:21)

Error: exit status 1
ERROR: exit status 1

When I try to get logs from pod I got error:
Get "https://microk8s-master-3:10250/containerLogs/<pod_name>?follow=true&tailLines=100&timestamps=true": dial tcp: lookup microk8s-master-3: Temporary failure in name resolution

K4Prox add nodes dns to /etc/hosts but it's reverted to default by cloud-init.
Hosts should be added to /etc/cloud/templates/hosts.debian.tmpl not /etc/hosts

Tried to deploy k8s-dashboard, failed.

Went to manually do it and realized it needed to be tagged correctly, deleted and created nearly the same helm app.

Error is stating repo already exists.

I know how to clear this in CLI, however seems like a user facing bug.

For those in need

helm repo remove

Hi,

    My intention here is to add a "orphan" worker node to join the cluster on my own since the wizard steps do not allow a workflow to add additional worker node.

Unless you tell me there is a proper workflow to do what I intend to do : is to add additional worker node into the cluster.

Hi,

        I have tried testing this a few times on my proxmox cluster but keep getting different type of errors. I am attaching a screenshot of the error that I am facing now. I try to find the log files but not sure where does it keep it.