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
{{ message }}
This repository was archived by the owner on Aug 26, 2022. It is now read-only.
Suggested Remediation|Ensure that your container has passed the Red Hat Container Certification Program (CCP).
100
100
Best Practice Reference|[CNF Best Practice V1.2](https://connect.redhat.com/sites/default/files/2021-03/Cloud%20Native%20Network%20Function%20Requirements.pdf) Section 6.3.7
101
+
#### helmchart-is-certified
102
+
103
+
Property|Description
104
+
---|---
105
+
Test Case Name|helmchart-is-certified
106
+
Test Case Label|affiliated-certification-helmchart-is-certified
Description|http://test-network-function.com/testcases/affiliated-certification/helmchart-is-certified tests whether helm charts listed in the cluster passed the Red Hat Helm Certification Program.
110
+
Result Type|normative
111
+
Suggested Remediation|Ensure that the helm charts under test passed the Red Hat's helm Certification Program (e.g. listed in https://charts.openshift.io/index.yaml).
112
+
Best Practice Reference|[CNF Best Practice V1.2](https://connect.redhat.com/sites/default/files/2021-03/Cloud%20Native%20Network%20Function%20Requirements.pdf) Section 6.2.12 and Section 6.3.3
Description|http://test-network-function.com/testcases/lifecycle/liveness Checks that all pods under test have a liveness probe defined.
173
+
Result Type|normative
174
+
Suggested Remediation|Ensure that all CNF's pods under test have a liveness probe defined.
175
+
Best Practice Reference|[CNF Best Practice V1.2](https://connect.redhat.com/sites/default/files/2021-03/Cloud%20Native%20Network%20Function%20Requirements.pdf) Section 6.2
Suggested Remediation|Choose a terminationGracePeriod that is appropriate for your given CNF. If the default (30s) is appropriate, then feel free to ignore this informative message. This test is meant to raise awareness around how Pods are terminated, and to suggest that a CNF is configured based on its requirements. In addition to a terminationGracePeriod, consider utilizing a termination hook in the case that your application requires special shutdown instructions.
211
235
Best Practice Reference|[CNF Best Practice V1.2](https://connect.redhat.com/sites/default/files/2021-03/Cloud%20Native%20Network%20Function%20Requirements.pdf) Section 6.2
Description|http://test-network-function.com/testcases/lifecycle/readiness Checks that all pods under test have a readiness probe defined.
245
+
Result Type|normative
246
+
Suggested Remediation|Ensure that all CNF's pods under test have a readiness probe defined.
247
+
Best Practice Reference|[CNF Best Practice V1.2](https://connect.redhat.com/sites/default/files/2021-03/Cloud%20Native%20Network%20Function%20Requirements.pdf) Section 6.2
Suggested Remediation|Ensure that the CNF is able to communicate via the Multus network(s). In some rare cases, CNFs may require routing table changes in order to communicate over the Multus network(s). To exclude a particular pod from ICMPv4 connectivity tests, add the test-network-function.com/skip_connectivity_tests label to it. The label value is not important, only its presence.
250
286
Best Practice Reference|[CNF Best Practice V1.2](https://connect.redhat.com/sites/default/files/2021-03/Cloud%20Native%20Network%20Function%20Requirements.pdf) Section 6.2
Description|http://test-network-function.com/testcases/networking/icmpv6-connectivity checks that each CNF Container is able to communicate via ICMPv6 on the Default OpenShift network. This test case requires the Deployment of the debug daemonset.
296
+
Result Type|normative
297
+
Suggested Remediation|Ensure that the CNF is able to communicate via the Default OpenShift network. In some rare cases, CNFs may require routing table changes in order to communicate over the Default network. To exclude a particular pod from ICMPv6 connectivity tests, add the test-network-function.com/skip_connectivity_tests label to it. The label value is not important, only its presence.
298
+
Best Practice Reference|[CNF Best Practice V1.2](https://connect.redhat.com/sites/default/files/2021-03/Cloud%20Native%20Network%20Function%20Requirements.pdf) Section 6.2
299
+
#### icmpv6-connectivity-multus
300
+
301
+
Property|Description
302
+
---|---
303
+
Test Case Name|icmpv6-connectivity-multus
304
+
Test Case Label|networking-icmpv6-connectivity-multus
Description|http://test-network-function.com/testcases/networking/icmpv6-connectivity-multus checks that each CNF Container is able to communicate via ICMPv6 on the Multus network(s). This test case requires the Deployment of the debug daemonset.
308
+
Result Type|normative
309
+
Suggested Remediation|Ensure that the CNF is able to communicate via the Multus network(s). In some rare cases, CNFs may require routing table changes in order to communicate over the Multus network(s). To exclude a particular pod from ICMPv6 connectivity tests, add the test-network-function.com/skip_connectivity_tests label to it.The label value is not important, only its presence.
310
+
Best Practice Reference|[CNF Best Practice V1.2](https://connect.redhat.com/sites/default/files/2021-03/Cloud%20Native%20Network%20Function%20Requirements.pdf) Section 6.2
251
311
#### service-type
252
312
253
313
Property|Description
@@ -260,6 +320,18 @@ Description|http://test-network-function.com/testcases/networking/service-type t
260
320
Result Type|normative
261
321
Suggested Remediation|Ensure Services are not configured to use NodePort(s).
262
322
Best Practice Reference|[CNF Best Practice V1.2](https://connect.redhat.com/sites/default/files/2021-03/Cloud%20Native%20Network%20Function%20Requirements.pdf) Section 6.3.1
323
+
#### undeclared-container-ports-usage
324
+
325
+
Property|Description
326
+
---|---
327
+
Test Case Name|undeclared-container-ports-usage
328
+
Test Case Label|networking-undeclared-container-ports-usage
Description|http://test-network-function.com/testcases/networking/undeclared-container-ports-usage check that containers don't listen on ports that weren't declared in their specification
332
+
Result Type|normative
333
+
Suggested Remediation|ensure the CNF apps don't listen on undeclared containers' ports
334
+
Best Practice Reference|[CNF Best Practice V1.2](https://connect.redhat.com/sites/default/files/2021-03/Cloud%20Native%20Network%20Function%20Requirements.pdf) Section 16.3.1.1
Copy file name to clipboardExpand all lines: Makefile
+7-5
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ COMMON_GO_ARGS=-race
47
47
GIT_COMMIT=$(shell git rev-list -1 HEAD)
48
48
GIT_RELEASE=$(shell git tag --points-at HEAD | head -n 1)
49
49
GIT_PREVIOUS_RELEASE=$(shell git tag --no-contains HEAD --sort=v:refname | tail -n 1)
50
-
GOLANGCI_VERSION=v1.44.0
50
+
GOLANGCI_VERSION=v1.44.2
51
51
52
52
# Run the unit tests and build all binaries
53
53
build:
@@ -78,8 +78,7 @@ lint:
78
78
# Build and run unit tests
79
79
test: mocks
80
80
go build ${COMMON_GO_ARGS} ./...
81
-
go test -coverprofile=cover.out -covermode count `go list ./... | grep -v "github.com/test-network-function/test-network-function/test-network-function"| grep -v mock`
82
-
go tool cover -func cover.out
81
+
UNIT_TEST="true" go test -coverprofile=cover.out ./...
83
82
84
83
coverage-html: test
85
84
go tool cover -html cover.out
@@ -126,10 +125,13 @@ update-deps:
126
125
127
126
# Install build tools and other required software.
0 commit comments