-
The calico-node daemonset has terminationGracePeriodSeconds set.
In the manifest version, it's coded as 0:
`
terminationGracePeriodSeconds: 0
`
But in the version generated by tiger…
-
**Is your feature request related to a problem? Please describe.**
Monitoring calico and calico-typha is a must, as it is a critical service that if it goes down, it will take down the networking o…
-
Before digging into this, is calico required? Docs say it is optional and default turned off, however, it installs.
If required, pointers in debugging the error welcome and happy work through it. I've…
-
**Describe the bug**
On AKS clusters with calico enabled a namespace calico-system is created. Within that we can find a deployment calico-kube-controllers. This deployment is currently labels twice …
-
## Expected Behavior
when pod startup, connect to cluster ip should ok. but now after a little ms the network being ok.
## Current Behavior
Within a few milliseconds after pod startup, …
-
**What happened**:
Autoscaling seems to scale to maximum capacity as soon as the ingress controller is deployed.
**What you expected to happen**:
Not seeing the ingress scale immediat…
-
I tried using the new built-in `NetworkPolicy` support in v0.24.0 (#842 / #3612) instead of Calico. It did not work well, apparently due to DNS problems.
**What happened**:
Requests to either po…
-
### Is your feature request related to a problem? Please describe.
I've changed my calico CNI configuration from `overlay: Always` to `overlay: CrossSubnet`. I'm aware that k0s does not currently s…
-
We have an AWS multi-region instance. We are trying to install the application across the regions and the deployment is getting filed due to MTU auto-detection enabled in cni.
## Expected Behavior
…
-
**What kind of request is this (question/bug/enhancement/feature request):**
Bug
**Steps to reproduce (least amount of steps as possible):**
- Create a Rancher provisioned custom cluster …
axeal updated
4 months ago