kubefirst cli should install mkcert without a secondary step in docs, even if it means sudo prompt

[johndietz]

What is your feature idea?

i think mkcert is the only prerequesite tool that prevents our users from installing the cli, and running kubefirst launch up and kubefirst k3d create without reading any docs. even if there are others, we should remove this manual setup step.

Why is it needed?

ux

Is this missing feature preventing you from using kubefirst?

• Yes

Code of Conduct

• I agree to follow this project's Code of Conduct

[patrickdappollonio]

Would love to know more about this. One of the things we could definitely do is import mkcert ourselves and do the management in code rather than downloading yet another binary.

[jokestax]

can we do it as a step as a preflight check and ask for sudo password in the form of good ui (https://github.com/charmbracelet/huh) ?

[fharper]

duplicate of #1987 but I'll close the other issue even if it's older since people started to discuss here instead...

I remember when I proposed this the day we added mkcert as a prerequisite (so even before I created the issue in January), some people on the team (It was either @johndietz , @jarededwards or Scott) didn't want this, but I can't remember the reason. I think it was because we needed sudo, which I didn't see as an issue: many CLI require it for different steps.