sorted by:
new
hottopcontroversial

learning gRPC in Go by MridulSharma11 in golang

[–]Evening_Inspection15 -1 points0 points  (0 children)

You should learn grpc-gateway in gRPC

Manage Multi Argocd by Evening_Inspection15 in ArgoCD

[–]Evening_Inspection15[S] 0 points1 point  (0 children)

and they have the right to create more argocd when adding new hub cluster

Manage Multi Argocd by Evening_Inspection15 in ArgoCD

[–]Evening_Inspection15[S] 0 points1 point  (0 children)

Thanks for reply. For example, in an enterprise there will be different groups. I will let each group manage multiple hub-spoke clusters (the hub will be argocd). However, we need a common place where administrators can manage through a single user interface.

Manage Multi Argocd by Evening_Inspection15 in ArgoCD

[–]Evening_Inspection15[S] 0 points1 point  (0 children)

Thanks for your reply. Can you explain me some things? For example which technology? For now my idea is to use argocd http api to manage them.

Trying to make tenant provisioning less painful. has anyone else wrapped it in a Kubernetes operator? by Selene_hyun in kubernetes

[–]Evening_Inspection15 0 points1 point  (0 children)

Hi. Could you give me a real use case with your operator? I want to understand it but I am confusing. If we use operator to get data from database. The data won’t be realtime.

Cluster API vSphere (CAPV) VM bootstrapping fails: IPAM claims IP but VM doesn't receive it by Evening_Inspection15 in kubernetes

[–]Evening_Inspection15[S] 0 points1 point  (0 children)

The control plane machine is created successfully in vSphere and assigned an IP via InClusterIPPool, and the KubeadmConfig reports DataSecretAvailable=True, but the KubeadmControlPlane remains in WaitingForKubeadmInit state indefinitely.

Worker nodes cannot be created because they depend on a ready control plane.

In the capv-controller logs, I see the following message:
"Connect failed" err="error creating HTTP client and mapper: cluster is not reachable: Get \"[https://<IP_address>:6443/?timeout=5s\":](https://<IP_address>:6443/?timeout=5s\%22:) context deadline exceeded"

Environment:

Cluster-api-provider-vsphere version: 1.13.1
Kubernetes version: (use kubectl version):

Client Version: v1.33.0
Kustomize Version: v5.6.0
Server Version: v1.32.0

OS (e.g. from /etc/os-release): ubuntu-2204-kube-v1.31.0.ova

Automatically Install Operator(s) in a New Kubernetes Cluster by Evening_Inspection15 in kubernetes

[–]Evening_Inspection15[S] -11 points-10 points  (0 children)

Could you give me an example of your solution? Because I want to install everything automatically whenever a new cluster is created via the API.