-
## Describe the bug (🐛 if you encounter this issue)
Some longhorn-manager pods timeout when accessing NFS server for backups.
## To Reproduce
Initialize Longhorn 1.5.1 via Helm chart. Some lo…
-
## Summary
Since version 7.0.0, the DNS resolution is no longer properly done in Kubernetes. For example, a resource, such as Git, that refers to an external URL will not be able to read from a rem…
-
**What happened**:
Reopening issue which is the same as #4832
I defined an ingress resource with a server alias on a separate domain, using the nginx.ingress.kubernetes.io/server-alias…
-
### Browsertrix Version
v1.11.3-12f994b
### What did you expect to happen? What happened instead?
When you download wacz files using the API you get wacz filenames like "20230225142507561-manual-20…
-
**Rancher Server Setup**
- Rancher version: 2.7.9 with cherry picked changes #43582
- Installation option (Docker install/Helm Chart): Helm / EKS
**Information about the Cluster**
- Kubernetes v…
dvob updated
7 months ago
-
### Version
__Karpenter Version:__ v0.0.0
__Kubernetes Version:__ v1.0.0
### Expected Behavior
the pod on new karpenter node, /etc/resolv.conf is 10.0.0.10. not follow az cli create --dns-se…
-
### Use case:
Complex applications may have nested dependencies between the different charts. As the dependencies are visible by recursively scanning the charts, it can be naturally desired to assemb…
-
ref: [Default certificate does not exist #601](https://github.com/haproxytech/kubernetes-ingress/issues/601)
On haproxy ingress controller v1.10.10 I get this error in logs:
ERROR global.go:272 …
-
I have IAM service account with automount token which allows to use KMS to decrypt sops file. When I'm running helm secrets decrypt on repo container, I can see decrypted values. The issue is when I'm…
-
The current Helm templates deploy the Nginx ingress controller and expose it with a Service of type LoadBalancer. This is fine for production-grade environments where the Kubernetes clusters have exte…