Abhishek Gupta

Ah I see! Thanks @zhxu2

> Did the hpa creation succeed? Try kubectl get hpa > https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#how-does-the-horizontal-pod-autoscaler-work > No, the HPA was not created > I tried with the example here https://github.com/oam-dev/rudr/blob/ac239fcfd2056a9e593b90737a3c8a582b38346f/examples/autoscaler.yaml > and it...

As mentioned in the issue details, I am not sure if Rudr is built to "work with KEDA" natively (I maybe be wrong so please correct me and point me...

> into your app cfg, > I think if you decide to include vol mounter trait such as: > traits: > - name: volume-mounter > properties: > volumeName: emphemeral-vol >...

> I think the bug is that a trait acts without any context in the current rudr implementation. Each trait's action is pre determined regardless of the component it applies...

Facing the same issue.. Any resolution yet ? `nodetool status` returns the internal IP of the VM where Cassandra is running. `gocql` fails but I am able to connect successfully...

ok.. finally resolved this by setting `DisableInitialHostLookup` to true

This is what I am referring to as static e.g. if node1 is started as follows `gnatsd -p 4222 -cluster nats://node1:4248`, how will it be possible to the system to...