-
**What happened and what you expected to happen**:
What happened:
keadm join --cloudcore-ipport=192.168.11.73:10000 --kubeedge-version=v1.18.0 -t 3f745d2d46cff9a3d77b23ed53aa0e1f5cb17d1618e275b954…
-
### What happened?
A kubernetes cluster deployed in AWS is subject to occasional zonal [outages](https://aws.amazon.com/premiumsupport/technology/pes/). In the most kubernetes cluster setup usecase…
-
**Distribution (run `cat /etc/os-release`):**
Pop!_OS 22.04
**Related Application and/or Package Version (run `apt policy $PACKAGE NAME`):**
N/A
**Issue/Bug Description:**
When b…
-
**Screenshots**
**Operating System**
**Additional context**
-
Came across this when mucking about with `make deploy using=globalnet,lighthouse` in the operator repo.
**What happened**:
The broker has components listed twice:
```
kubectl --context=clus…
-
... and which further steps should be done after the deployment of heimdall
-
### Describe the bug
I am getting NSXT different authentication errors during the plan and apply phase.
Getting "Error: Failed to retrieve NSX version (403 ). Please check connectivity and authent…
-
This is a somewhat simplified scenario, but I would like to know how people deal with these kinds of problems.
I have a docker swarm consisting of 3 managers and a service that
writes to a networ…
-
Hi all,
how about to set hw_qemu_guest_agent = yes as default on images that come with the image manager?
The background is that this is a required setting on the source image if a cloud has a r…
-
I am using Wazuh-Manger 3.12.3. When the agent and Manager is in same network then the agents are successfully connected with the manager but when agent is different network then, there is no connec…