-
This issue shifted focus. This is now an issue for creating a dedicated helm chart for opentelemetry CRDs.
-
Timoni **apply** will just pass through while waiting for CRD resource to become ready.
The problem is not that timoni won't wait, but that CRD operator won't be fast enough to set status condition…
-
### Problem Description
Kubernetes has been deprecating API(s), which will be removed and are no longer available in 1.22. Operators projects using [these APIs](https://kubernetes.io/docs/reference/…
-
#### Context
All ACK controllers start out with an Alpha API version (`v1alpha1`) that evolves from release to release, most likely due to updates in `aws/aws-sdk-go` OpenAPI Schemas or because of …
-
It would be neat if we could add a folder filled with k8s resources to eks cluster.
```
kubectl apply -k "github.com/aws/eks-charts/stable/aws-load-balancer-controller//crds?ref=master"
```
…
-
### Component(s)
target allocator
### What happened?
## Description
Upgrading spec to v1beta1 and deploying spec, new targetallocator stops picking up all PodMonitor and ServiceMonitor definitions…
-
This logic existed before b/c the operator had GatewayClass/Gateway controllers but they no longer exist.
Options:
- Leave as-is, if Gateway API or other CRDs we depend on don't exist, Contour wil…
-
## Description
Currently `clientinfo` chain element can work with CLUSTER_NAME env https://github.com/networkservicemesh/sdk/blob/main/pkg/tools/clientinfo/clientinfo.go#L30
But we dont use it…
-
v1beta2 is marked as (working version, not fixed), is there a timeline for when it will be?
Additionally, does `working version` imply that v1beta2 might take incompatible changes?
-
As support for the Gateway API progressed, we needed to redesign the structure of `pkg/ingress`.
This directory now has multiple types of resources mixed together: Kubernetes native resources, APISIX…