You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we start tests with the parameter --namespace chainsaw-tests, we get the error that the namespace already exist. This is correct, the namespace does already exist, but it should just run inside this namespace.
We have this behaviour when the tests are started in the official container, not when launched from a client where chainsaw is installed through brew.
Also; the pod doesn't exit with a error code; so Kubernetes says the pod is completed instead of failed (normally, when a test fails, the pod fails).
Steps to reproduce
Put the test files in the container (for example with a Dockerfile)
FROM ghcr.io/kyverno/chainsaw:v0.2.8
`COPY chainsaw-tests/ /chainsaw-tests/`
Create manually a namespace chainsaw-tests
Launch the container/pod with the following commands:
chainsaw version Version
v0.2.8
Description
When we start tests with the parameter
--namespace chainsaw-tests
, we get the error that the namespace already exist. This is correct, the namespace does already exist, but it should just run inside this namespace.We have this behaviour when the tests are started in the official container, not when launched from a client where chainsaw is installed through brew.
Also; the pod doesn't exit with a error code; so Kubernetes says the pod is completed instead of failed (normally, when a test fails, the pod fails).
Steps to reproduce
chainsaw-tests
When trying with <=v.0.2.7, it does work. Also tried with 0.2.9 and x.10, doesn't solve it.
Expected behavior
Chainsaw tests would run in the provided namespace.
Screenshots
No response
Logs
Slack discussion
No response
Troubleshooting
The text was updated successfully, but these errors were encountered: