-
**1. Describe IN DETAIL the feature/behavior/change you would like to see.**
Kubernetes best practices state that kube-proxy is best deployed as a DaemonSet. As kops - as of now - places the kube-pro…
-
It seems when using the helm chart it is not possible to add this to the DaemonSet:
env:
- name: NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
-> an…
-
### There are 3 Nodes in cluster, create one Daemonset (Name: my-pod, Image: nginx) on each node except one (Woker-node-3)
```
kubectl taint node worker-node-3-cgaga env=qa:NoSchedule
kubectl de…
-
**Is your feature request related to a problem? Please describe.**
On our environment we need to make use of Huge Pages, this is because we never want to swap out the Huge Pages, they must be statica…
-
**DESCRIPTION:**
If multi-socket systems are used the respective platforms (bare metal server) need to be registered with the [Intel Registration Service](https://api.portal.trustedservices.intel.c…
-
We are using Kueue with DWS on a GKE cluster for managing GPU instances. Our [application](https://github.com/skypilot-org/skypilot) relies on accessing `/dev/fuse` exposed through a [daemonset](https…
-
**Describe the bug**
Maybe it is a bug, maybe it is an edge case. I am also interested in (different) solutions of other users.
Given are 3 nodes with `different interface names`, e.g. `eth0`, `en…
-
https://github.com/hashicorp/consul-k8s/blob/20a23977648faece1f4b8f62341d5eef43cba9a3/charts/consul/templates/client-daemonset.yaml#L448-L450
Disabling gRPC in client is not disabling node port 850…
-
When adding new nodes to the cluster, the calico pods keeps on failing. Even upon deletion as well as restarting the `calico-node` daemonsets it keeps failing. The old pods are not susceptible to a …
-
I can't seem to get the healthcheck port exposed for some reason. I'm creating the release in terraform:
```hcl
locals {
collector_version = "0.104.0"
}
resource "helm_release" "opentelemet…