-
**Problem description (if applicable)**
In order to protect the environment, pre-determined calico policies will need to be in place, as desired. For any un-planned/un-tested/accidental policy change…
-
To make Calico compatible with Submariner, it needs to create Calico IP pools for the subnets associated with the Pod and Service CIDRs of the remote clusters[1].
We want to make it easier to deplo…
-
### Describe the bug
During heavy log volumes, e.g. >10k log entries per second, fluentd consistently drops logs. It may be related to log rotation (on Kubernetes). When I ran a load test, I see th…
-
### Description
I plan to use Windows containers, and I have prepared Windows nodes as well as the Calico network plugin. However, the Pod scheduled to the Windows node fail to create. When I use t…
-
**文档版本**
v1.16
**现象描述**
kubectl get nodes命令执行后，集群是 NotReady，不知如何进行问题查找
NAME STATUS ROLES AGE VERSION
k8s-master NotReady 22h v1.16.6
k8s-node-01 NotReady 22h…
-
Upon installing Tigera Operator in my EKS cluster on AWS with kube-apiserver-audit logs enabled, I noticed a significant increase in log volume. These logs are being pushed to CloudWatch, leading to a…
-
**Environment**
- Calico/VPP version: 3.26.0
- Kubernetes version: 1.28.3
- Deployment type: On-prem VM
- Network configuration: Calico / want to do SRv6 but haven't gotten there yet
- Containerd…
-
## Expected Behavior
Current Calico resources deployed by manifests are migrated to Calico operator CRD.
## Current Behavior
Tigera status shows these messages:
```
$ kubectl de…
-
**What happened**:
```shell
kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system calico-kube-c…
-
Our logging agents current have a rate limit of 10 messages/s that calico-apiserver breaks occasionally. We would like to be able to set the log level for calico-apiserver component to not log INF…