-
*Installation details*
HEAD: e5edf3086982424faeff019d21590c302002d019
*Description*
Speculative read retry causes more trouble than good.
In particular, if there is either a long enough slownes…
-
**How to categorize this issue?**
/area open-source dev-productivity
/kind enhancement
**What would you like to be added**:
We should upgrade to the latest versions of our go upstream depe…
-
**What happened**:
I want to use strict NetworkPolicy to restrict my network in EKS cluster, at the same time I use some 3rd applications that have admission controller, they were called by control…
-
I've been using this provider to deploy kubernetes clusters on top of Proxmox VMs for a while now. Recently I tried deploying a cluster to do some testing and ran into the following error and now I ca…
-
**What would you like to be added**:
Run the entire conformance test suite when a PR is raised on Gateway API implementations, but run it as a non blocking step.
**Why this is needed**:
As a …
-
**What happened**:
I've noticed the **Priority** field in the response of the Info service, which can be used for sorting. However, currently, sortCallbacksPerHookPoint sorts based on the **HookPoi…
-
**Describe the bug**
getting this output that indicates port is in use
I checked using netstat and I do not see it being used
I am using wsl
I checked bot wsl and windows os the port is not being…
-
## Describe the bug
Non-existing block device results in longhorn-manager pods to be in `Crashloopbackoff` state.
When longhorn-manager pods are in `Crashloopbackoff`, users are unable to update t…
-
**User Story**
As an operator I would like to update the cluster network configuration for an existing Cluster resource for upgrading a single stack Cluster to a dual-stack Cluster.
**Detail…
-
When `sc install` is executed, controller-manager is not AVAILABLE.
The controller-manager pod is CrashLoopBackOff.
Error message is below.
```
"error running controllers: failed to get api ver…