Add more chainsaw e2e tests.#4422
Conversation
|
|
||
| ## To run the test: | ||
| ``` | ||
| chainsaw test --values ../values.yaml --namespace postgres-operator --config ../config.yaml |
There was a problem hiding this comment.
❓ I'm not sure which makes more sense, but I think we either need to update the files we already have and then adjust the paths here or otherwise add additional values.yaml and config.yaml files in the appropriate sub-directories.
This would apply to the README files throughout.
There was a problem hiding this comment.
Yeah I deleted all of the subdirectory values/config files because they were all just duplicating each other. Really only need the ones in the root folder. But I will update the readmes accordingly.
There was a problem hiding this comment.
looks like the main values.yaml file needs atleast pgbackrest to it? I'm only seeing the postgres image reference in it currently.
There was a problem hiding this comment.
I've removed all image references other than for a psql image. That way these tests use whatever related images are set by the PGO installer.
…kuttl and chainsaw support go 1.26).
… chainsaw flag. Skip autogrow tests in github actions ci. Add README and makefile note about skipping autogrow tests when running in k8s cluster that does not support volume expansion. Reorganize autogrow tests.
dsessler7
force-pushed
the
add-weekly-readiness-tests
branch
from
151b8e0 to
bd87c63
Compare
4 participants
Checklist:
Type of Changes:
What is the current behavior (link to any open issues here)?
We have some chainsaw tests.
What is the new behavior (if this is a feature change)?
We have more chainsaw tests.
Other Information: