Container Security Operator

[alecmerdler]

Previously added to upstream-community-operators here.

Signed-off-by: alecmerdler [email protected]

Thanks submitting your Operator. Please check below list before you create your Pull Request.

---

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

---

New Submissions

• Has you operator nested directory structure?
• Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
• Are you familiar with our contribution guidelines?
• Have you packaged and deployed your Operator for Operator Framework?
• Have you tested your Operator with all Custom Resource Definitions?
• Have you tested your Operator in all supported installation modes?
• Is your submission signed?

Your submission should not

• Modify more than one operator
• Modify an Operator you don't own
• Rename an operator - please remove and add with a different name instead
• Submit operators to both upstream-community-operators and community-operators at once
• Modify any files outside the above mentioned folders
• Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

1. Description about the managed Application and where to find more information
2. Features and capabilities of your Operator and how to use it
3. Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

• Human readable name and 1-liner description about your Operator
• Valid category name¹
• One of the pre-defined capability levels²
• Links to the maintainer, source code and documentation
• Example templates for all Custom Resource Definitions intended to be used
• A quadratic logo

[gallettilance]

/lgtm

[gallettilance]

/cc @jozzi

[gallettilance]

/cc @J0zi

[openshift-ci-robot]

New changes are detected. LGTM label has been removed.

[alecmerdler]

@gallettilance Needed to add alm-examples annotation to fix scorecard.

[aneeshkp]

/retest

[alecmerdler]

===== Test: operator-scorecard-tests =====

 The operator failed the minimal scorecard criteria of passing the 'Spec Block Exists' and 'Status Block Exists' basic tests.

 time="2019-12-17T20:41:31Z" level=warning msg="Could not load config file; using flags"
time="2019-12-17T20:41:31Z" level=warning msg="Plugin directory not found; skipping external plugins: stat scorecard: no such file or directory"
time="2019-12-17T20:42:35Z" level=error msg="Plugin `olm-tests` failed with error (failed to read file: /tmp/944692770.cr.yaml)"
Basic Tests:
	Spec Block Exists: 1/1
	Status Block Exists: 0/1
	Writing into CRs has an effect: 0/1
Failed Plugin: olm-tests:

Total Score: 21%
�[33mSUGGESTION:�[0m Add a 'status' field to your Custom Resource
�[33mSUGGESTION:�[0m The operator should write into objects to update state. No PUT or POST requests from the operator were recorded by the scorecard.
 

======== Debug output of the operator container =========

This Operator is designed to fully control the CRs it's managing (effectively read-only, but CRs don't support that). Users are not intended to create/modify/delete ImageManifestVulns; instead the Operator creates them if any Pods on the cluster are running vulnerable container images.