Frédéric Harper comments

Results 359 comments of


                                            Frédéric Harper

Deploy Kubefirst as a Kubernetes Operator to Enable Broad Distribution Support

Thanks for the idea @codespearhead. I'll let @johndietz or @jarededwards comment on this one.

Cluster creation often timeout waiting for Argo CD or Vault

When it timeout on Vault, here is the error + the state of the cluster (see no Vault pod at all yet). ![CleanShot 2024-07-08 at 14 56 24@2x](https://github.com/kubefirst/kubefirst/assets/1170989/31731712-288b-4429-9a35-b60bc9c5e4ae) ![CleanShot 2024-07-08...

Cluster creation often timeout waiting for Argo CD or Vault

It may be useful information, but Argo CD or Vault never time out when creating a cluster on K3s, while with k3d + public clouds, I get timeout 4+ out...

Cluster creation often timeout waiting for Argo CD or Vault

While writing my previous comment, I just remembered that @jokestax may have found the issue, and shared this with us during's today standup. I don't remember all the details, but...

Cluster creation often timeout waiting for Argo CD or Vault

This [PR](https://github.com/kubefirst/kubefirst-api/pull/363) will fix the issue for public clouds, but not k3d. Maybe once we remove runtime in favor of the API, k3d timeout won't be a problem anymore.

Vault certificate secret issue

@jokestax: FYI

Vault certificate secret issue

We also had an user who had this issue with AWS.

Bug: Using the Gitops-template repository in private conditions

Sorry, we missed that issue. It's probably a bug, maybe the CLI isn't using the token for fetching the `gitops-template` repository. It should work though if you provide a token...

Bug: Using the Gitops-template repository in private conditions

I can reproduce the issue, let me check with the engineering team.

Validate CIVO cluster requirements before creating the environment

Thanks for the suggestion @agalue. It is something we could add to the pre-flight check I think.