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
Run with the spinach.yaml passed in .\popeye.exe --save --out html -l warn -f .\spinach.yaml
Container isn't picked up by configuration, fails back to showing non-matched deployment
Expected behavior
(I think) it should allow filtering to containers, unless this is a limitation of the deployments API and the way they're referenced in its spec.
Can confirm that this only seems to allow filtering of error codes for specific containers when used under excludes.v1/pods
Have attempted to use the pattern described by the OP to filter error codes under specific containers for daemonsets, deployments and statefulsets and this does not work.
Describe the bug
Can't filter containers in spinach.yaml for deployments. Filtering by deployment FQN or code works as expected.
To Reproduce
.\popeye.exe --save --out html -l warn -f .\spinach.yaml
As expected, the warn isn't there
Run with the spinach.yaml passed in
.\popeye.exe --save --out html -l warn -f .\spinach.yaml
Container isn't picked up by configuration, fails back to showing non-matched deployment
Expected behavior
(I think) it should allow filtering to containers, unless this is a limitation of the deployments API and the way they're referenced in its spec.
Versions (please complete the following information):
Additional context
Ideally we don't want to filter the whole deployment or popeye code, as any other containers would require limits/requests
The text was updated successfully, but these errors were encountered: