Kubefirst mongodb Username and Password not set for arm builds

[EamonKeane]

Kubefirst mongodb Username and Password not set for arm builds

[fharper]

This is fixed with your solution, thanks. It will be available in the next release.

[fharper]

Thanks for creating the issue @EamonKeane. Our team will give it a closer look soon!

[fharper]

Just to be sure, you are taking about installing the kubefirst console UI to create a new cluster (as in the steps listed at https://docs.kubefirst.io/civo/quick-start/install/ui in the "Helm (ARM / M1 Mac / M2 Mac)" tab, right? If it's the case, it's not using the GitOps catalog: the catalog only helps you to install new applications to your created management cluster.

In the case, when exactly do you get the log-in issue? I tried to replicate, and when following the steps listed in the documentation I shared, even when killing all pods, the console still work as intended. Or is it after you created a cluster with the console UI?

[EamonKeane]

I used the regular cli install. The easiest way to reproduce is to install using the cli, and then port-forward the mongodb container to a database viewer (e.g. Datagrip). Try use the login credentials that are listed on the kubefirst api pod. They won't work, because the user isn't created.

[fharper]

@EamonKeane: oh OK, now I understand, let me check if I can reproduce.

[fharper]

I can reproduce the same on my arm64 (MacBook M1 Pro). Let me check with the engineering team.

[fharper]

For other stumbling on this thread, that would explain that the provisioned services and the catalog in the console app are empty after a pod or cluster restart.