Rohit Verma

The issue starts resurfacing again, ``` 2021-06-12T07:59:02.740Z ERROR terraform-k8s Failed to update output status {"error": "workspaces.app.terraform.io \"s3-logs-ap-south-1\" not found"} github.com/go-logr/zapr.(*zapLogger).Error /go/pkg/mod/github.com/go-logr/[email protected]/zapr.go:128 github.com/hashicorp/terraform-k8s/workspacehelper.(*WorkspaceHelper).reconcileWorkspace /workspace/workspacehelper/workspace_helper.go:142 github.com/hashicorp/terraform-k8s/workspacehelper.(*WorkspaceHelper).Reconcile /workspace/workspacehelper/workspace_helper.go:442 github.com/hashicorp/terraform-k8s/controllers.(*WorkspaceReconciler).Reconcile /workspace/controllers/workspace_controller.go:63 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler /go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:244 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem...

If you look at the ingester_config as provided here https://cortexmetrics.io/docs/configuration/configuration-file/#ingester_config, you will observe that for a zone awareness, currently we need to provide the az per ingester. It meant that...

We can also use https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/ to ensure that pods are spread across as and then use the configmap with envfrom annotation value which would be correctly assigned.

A noob question, Can't we use istio, they have zone aware routing? And reduce the zone awareness functionalities from cortex? Similar functionalities are there in cilium too.

Faced same issue, unknowingly created a duplicate https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/2536

Is there any fix for this? Even in nightly builds?

It seems an imminent need, We recently tried to upgrade to CT 3.0. We observed that we are running out of SCP limitations of 5 per OU. Seems like CT...

@klrc can you give reference on how you solved with docker? Thanks

hi @samuelkarp even we are facing same issues with our microservices. It would be nice if we can push it further to 1048576 as mentioned here https://github.com/bottlerocket-os/bottlerocket/blob/084fc3b30ea7662029976ce8205fbadd6dadd91f/packages/containerd/1001-cri-set-default-RLIMIT_NOFILE.patch#L46. But couldn't find...

@zmrow we are also facing issues with rlimit on our elasticsearch clusters, and the current openfiles are shown as (-n) 65536. Is there a way to use the increased limit,...