-
The "cloud-provider-equinix-metal-kubernetes-external" service that the CCM creates when you enable the elastic IP for control plane nodes feature creates a service on port 443, not 6443. The EIP heal…
-
> We have encountered a provisioning failure for your device test1-g7tqp-master-0.
The PacketAPI returns:
```
403 You are not authorized to view this device
```
Right now the `MachineContro…
-
**How to categorize this issue?**
/area networking
/kind bug
/priority normal
/platform equinix-metal
**What happened**:
When creating 2nd or more shoot cluster, EIPs assigned to first clu…
-
**Description**
v3.0.1 of the Packet provider does not detect the network type correctly on device plans with more than two network ports (n2.xlarge.x86). Due to a recent change in the API, when de…
-
The only change to the default configuration is:
```
env:
- name: PACKET_LB
value: "kube-vip://"
```
```
E0203 12:50:44.392227 1 cloud.go:258] failed to up…
-
Get a error during ssh key creation, line 35 of the main.tf terraform script
line 35: "resource "metal_ssh_key" "ssh_pub_key" {"
i get a "error: not found". I noticed though that there is a publ…
-
While the API may need to be publicly exposed first (depends on #9) users would benefit from the ability to treat this provider like a module that can be plugged into broader solutions.
This will r…
-
**Description**
When deploying the prometheus-operator on a new Lokomotive cluster, the grafana pod is stuck in crashloop. It won't start because it's unable to retrieve the grafana-piechart-panel …
-
If API is unavailable during setup and for example we fail to fetch `kube-apiserver` namespace like in logs below, then CCM is running, but no Service will get IP address assigned until CCM is restart…
-
Device under test is a Packet c1.large.arm 96-core arm64 machine running Ubuntu 18.04.
```
ed@ed-2a-bcc-llvm:~$ go version
go version go1.11.2 linux/arm64
ed@ed-2a-bcc-llvm:~$ go get sigs.k8s.io…