Change note-quotes to admonitions

Author: mbuechse

contributor-docs/development/tests/conformance-tests-sonobuoy.md

@@ -6,17 +6,19 @@ Hence this reduces the effort required to establish SCS conformity to a minimum.
 
 In short this is achieved by storing all tests in a container image, which can then be called and launched on the clusters managed by sonoobuoy.
 
-> [!NOTE]
-> A more detailed description of why the SCS has decided to use sonobuoys can be found on the corresponding [Decsision Record][sonbouy-decision-record].
-> In addition, sonobuoy is also used as the toolset for executing Kubernetes very own [conformance tests][k8s-conformance].
+:::note
+A more detailed description of why the SCS has decided to use sonobuoys can be found on the corresponding [Decsision Record][sonbouy-decision-record].
+In addition, sonobuoy is also used as the toolset for executing Kubernetes very own [conformance tests][k8s-conformance].
+:::
 
 This document is intended to assist conformance test authors to integrate their tests into the sonobuoy framework.
 This requires a user to write the conformance tests in Golang, as this is the language provided by the framework itself.
 
 ## Step-by-step instructions for the development of sonobuoy tests using `docker` and `kind`
 
-> [!NOTE]
-> This guide refers to the brief instructions provided in the [standards repository][scs-sonobuoy-example-guide]
+:::note
+This guide refers to the brief instructions provided in the [standards repository][scs-sonobuoy-example-guide]
+:::
 
 ### Prerequisite
 
@@ -70,9 +72,11 @@ In general, SCS tests for KaaS are derived from standards that define certain ex
 As an example for this step-by-step guide, let's assume a scenario in which there is a fictional standard called "scs-0299-v1-example-standard.md".
 Pretend that the fictitious standard here stipulates that at least one pod MUST run in the namespace "namespace-test-a".
 
-> [!NOTE] 
-> The functions and behaviors to be tested MUST be precisely defined in a standard.
-> If you as a developer want to test something that you think is best tested but is not yet part of any standard, you MUST update the standard accordingly.
+:::note
+The functions and behaviors to be tested MUST be precisely defined in a standard.
+If you as a developer want to test something that you think is best tested but is not yet part of any standard, you MUST update the standard accordingly.
+:::
+
 
 #### 1. Create example test
 
@@ -87,9 +91,10 @@ First create a test file according to your standard and adhere to the naming con
 * The prefix MUST contain the name of the standard in lower case letters.
 * As a suffix, the file must end with "_test.go".
 
-> [!NOTE]
-> The suffix requirement comes from the go test framework itself. All test files must end with `_test.go`.
-> Otherwise they will not be selected by the test environment.
+:::note
+The suffix requirement comes from the go test framework itself. All test files must end with `_test.go`.
+Otherwise they will not be selected by the test environment.
+:::
 
 As an example, we will create a file for the fictitious standard "scs-0299-v1-example-standard.md" as follows:
 
@@ -102,11 +107,12 @@ As an example, we test here whether there are more than zero pods in the namespa
 The execution of this test should fail by default as there should be no pods in the namespace and the namespace itself should not exist.
 The aim is to display the results of a failed test so that we can show their interpretation in a later step.
 
-> [!NOTE]
-> Attention!!!: in order for the framework to select the functions for testing, their names must begin with "TEST_" in accordance with the naming convention of the golang test framework.
-> The framework in use is [kubernetes-sigs/e2e-framework][e2e-framework].
-> They also provide examples. Before you start implementing your own tests, you should check whether you can use one of the examples as a starting point for your own implementation.
-> Have a look at: [kubernetes-sigs/e2e-framework/examples][e2e-framework-examples]
+:::danger
+In order for the framework to select the functions for testing, their names must begin with "TEST_" in accordance with the naming convention of the golang test framework.
+The framework in use is [kubernetes-sigs/e2e-framework][e2e-framework].
+They also provide examples. Before you start implementing your own tests, you should check whether you can use one of the examples as a starting point for your own implementation.
+Have a look at: [kubernetes-sigs/e2e-framework/examples][e2e-framework-examples]
+:::
 
 As an example of this step-by-step guide, copy the following text into the file `scs_0299_v1_example_standard_test.go`:
 
@@ -183,8 +189,9 @@ cat results/plugins/scsconformance/sonobuoy_results.yaml | yq
 Once all tests have been executed successfully, you can read the results and receive feedback.
 You can call up the results as follows:
 
-> [!NOTE]
-> TODO:!!! to be described in more detail
+:::todo
+to be described in more detail
+:::
 
 ### Clean up after
 
@@ -195,7 +202,7 @@ make dev-clean
 make dev-purge
 ```
 
-### (optional) Run all at once:
+### (optional) Run all at once
 
 In addition, you can trigger all processes from above with one command. There is a single target in the Makefile for this:
 
@@ -213,8 +220,9 @@ export TESTFUNCTION_CODE="0299"
 make test-function
 ```
 
-> [!NOTE]
-> [e2e-framework-examples]
+:::note
+See also [e2e-framework-examples]
+:::
 
 [sonobuoy]: https://sonobuoy.io/
 [sonbouy-decision-record]: https://github.com/SovereignCloudStack/standards/blob/main/Standards/scs-0200-v1-using-sonobuoy-for-kaas-conformance-tests.md