Skip to content

Commit

Permalink
Update Standards/scs-0200-v1-sonobuoy-kaas-conformance-tests.md
Browse files Browse the repository at this point in the history
Co-authored-by: cah-hbaum <95478065+cah-hbaum@users.noreply.github.com>
Signed-off-by: tonifinger <129007376+tonifinger@users.noreply.github.com>
  • Loading branch information
tonifinger and cah-hbaum authored Dec 7, 2023
1 parent df6e273 commit 81af4f3
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions Standards/scs-0200-v1-sonobuoy-kaas-conformance-tests.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,10 +33,10 @@ Additionally, the tests would need to be able to run inside a pod in the K8s clu

## Design Considerations

Among the different ways to create a Sonobuoy plugin, there are three potential approaches that might work best for us.
These are described in more detail below, where we discuss the pros and cons of each approach.
One of these three approaches must be chosen for implementation.
For the purposes of the investigation and the preparation of this decision record, there are examples(proof of work) for each different approach.
There are different approaches to create a Sonobuoy plugin, which are discussed below in order to find a best practice for the SCS project.
The documented approaches show one example each in order to give a better representation to the reader.

Sonobuoy provides plugin examples in the repository [https://github.com/vmware-tanzu/sonobuoy-plugins][sonobuoy-plugins-repo], which are referenced throughout this section.

#### _Option 1_ GO [1]: Pick framework from the Sonobuoy plugin examples

Expand Down

0 comments on commit 81af4f3

Please sign in to comment.