Vito Botta

icon indicating a website link https://mastodon.social/@vitobotta icon indicating an email [email protected]

icon company Lead Platform Architect at brella.io icon location Espoo, Finland icon location I am a passionate developer/architect and ethical hacker based in Espoo, Finland.

Results 140 comments of Vito Botta

If node as IP ending with 1, lo is selected as flannel interface

The PR has been merge, thanks again!

add flag to not disable metrics-server

@michaelfresco you guessed it right. The goal was to get a more "Standard" cluster, with not too much k3s specific things, so I have kept the extra software installed automatically...

add flag to not disable metrics-server

Project card ref. https://github.com/users/vitobotta/projects/4/views/1?pane=issue&itemId=59923702

[loki-stack] loki statefulSet with persistence enabled doesn't start right away due to not recognizing PVC is already bound to it

I have been having this problem for months every time I need to upgrade and I always end up uninstalling and reinstalling, losing the existing logs. Is there a solution...

[loki-stack] loki statefulSet with persistence enabled doesn't start right away due to not recognizing PVC is already bound to it

> @vitobotta in my case it would eventually resolves itself, I have simply switched to installing all the charts separately straight from grafana's repo (loki, grafana) Sometimes I managed to...

[loki-distributed] How to increase ingester disk space

Hi @trevorwhitney , I tried this now but get `Error: UPGRADE FAILED: cannot patch "loki-ingester" with kind StatefulSet: StatefulSet.apps "loki-ingester" is invalid: spec: Forbidden: updates to statefulset spec for fields...

Update README

Hi @aleksasiriski and thanks a lot for letting me know! I had no idea. If you can find where this is at now it would be great :)

Call first_master earlier and exclude from other_masters

Do you mind describing these changes a bit more? How do these solve the problem you highlighted in https://github.com/vitobotta/hetzner-k3s/issues/311 exactly? I am not keen with introducing a "first master index"...

Call first_master earlier and exclude from other_masters

Thanks again for the PR. I am closing because I handled this in a more robust way in https://github.com/vitobotta/hetzner-k3s/pull/348 for the upcoming new major version v2.0.0.

Deleting master1 destroys cluster

Sorry for the delay. This is indeed a scenario I hadn't come across. What you suggest might work the first time when master1 is being recreated so we use say...