Prashant Tiwari

I can see that IP Assigned to the load balancer pod on my machine is not 172.18.1.100.

We are using the terraform version From terraform version [v3.28.0](https://github.com/hashicorp/terraform-provider-aws/milestone/175) terraform plan will fail if the bucket name has underscores for AWS. [Link](https://github.com/hashicorp/terraform-provider-aws/pull/17562#issuecomment-778330260) to bugfix in terrafrom ticket. But upgrading...

Please go ahead.

I think I ended up creating another ticket by mistake. Apologies. But I have worked on this and created a pull request. I think.

# Options We have two options to achieve this: 1. [Horizontal Pod Autoscaler](https://learnk8s.io/autoscaling-apps-kubernetes) 2. [KEDA (Kubernetes-based Event-driven Autoscaling)](https://keda.sh/docs/2.13/) ## Option#1 Horizontal Pod Autoscaler based on external metrics and a load...

# Should this be part of conda-store? Regardless of the option we take, this can be moved upstream to conda-store. - Points in favour of moving this to conda-store 1....

We should agree on these before we start. Please suggest. Thanks.

# Notes on POC ## Installing KEDA: ``` helm repo add kedacore https://kedacore.github.io/charts helm install keda kedacore/keda --namespace dev ``` ## Scaled job spec: ``` apiVersion: keda.sh/v1alpha1 kind: ScaledObject metadata:...

I am getting the following error: ``` │ 2024-04-05T18:44:42Z ERROR Reconciler error {"controller": "scaledobject", "controllerGroup": "keda.sh", "controllerKind" │ │ : "ScaledObject", "ScaledObject": {"name":"scaled-conda-worker","namespace":"dev"}, "namespace": "dev", "name": "scaled-conda-work │ │ er",...

I have also tried TriggerAuthentication: ``` apiVersion: v1 kind: Secret metadata: name: conda-pg-credentials namespace: dev type: Opaque data: PG_PASSWORD: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxx" --- apiVersion: keda.sh/v1alpha1 kind: TriggerAuthentication metadata: name: keda-trigger-auth-conda-secret namespace: dev...