drasi wait incorrectly validates readiness when reusing query container names

[ruokun-niu]

Steps to reproduce

1. Installs Drasi
2. Create a new QueryContainer with a different index and the name default.
3. Run drasi wait querycontainer default
4. The waiting process should complete immediately

Observed behavior

When I create a new Query container that has the same name as an existing query container and wait for it to become ready using drasi wait, the drasi wait command will complete instantly, even when the new pod is not ready.

Installing Drasi...
-e 

Updating Query Host to use a Rocks Index...
✓ Apply: QueryContainer/default: complete
✓ Wait QueryContainer/default online.  <- Completes instantly
-e 

I suspect that drasi wait checked the status of the old pod (since both query containers have the same name` and assumed that it is ready.

Desired behavior

When I create a new Query container that has the same name as an existing query container and wait for it to become ready using drasi wait, the drasi wait command should wait until the new pod is ready and the old pod is teared down

Workaround

Using a different query container name

Drasi Version

v0.3.2

Operating system

No response

Additional context

No response

Would you like to support us?

• Yes, I would like to support you