Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README note on Scorecard tests #143

Merged
merged 1 commit into from
Apr 25, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -235,6 +235,10 @@ Run `make test`
3. Export the operator installed namespace (e.g., *openshift-workload-availability*) before running the e2e test:
`export OPERATOR_NS=openshift-workload-availability && make test-e2e`

### Run Scorecard tests

Run `make test-scorecard` on a running Kubernetes cluster to statically validate the operator bundle directory using [Scorecard](https://sdk.operatorframework.io/docs/testing-operators/scorecard/).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how do you run that command "on a cluster"?


## Troubleshooting

1. Watch the FenceAgentsRemediation CR [status conditions](#fenceagentsremediation-cr-status) value, message, and reason for better understanding whether the fence agent action succeeded and the remediation completed.
Expand Down
Loading