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
The cis-operator enables running CIS benchmark security scans on a Kubernetes cluster and generate compliance reports that can be downloaded.
4
-
Benchmarks tests and the execution logic lives on [rancher/security-scan].
3
+
The cis-operator enables running CIS benchmark security scans on a Kubernetes cluster and generate compliance reports that can be downloaded. Benchmarks tests and the execution logic lives on [rancher/security-scan](https://github.com/rancher/security-scan).
5
4
6
-
## Building
5
+
> [!IMPORTANT]
6
+
> **This project has been replaced by [rancher/compliance-operator](https://github.com/rancher/compliance-operator).**
7
+
> It is now in a **Security Maintenance Phase** for Rancher 2.10 and 2.11. No new features will be added.
7
8
8
-
`make`
9
+
---
9
10
11
+
## Migration
12
+
For Rancher v2.12.0+, the legacy CIS Benchmark App is replaced by the new **[Rancher Compliance App](https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/compliance-scan-guides)**. Please follow the official guide to migrate your custom profiles:
10
13
11
-
## Running
12
-
1. Install the custom resource definitions:
13
-
-`kubectl apply -f crds/`
14
-
2. Install the operator
15
-
`./bin/cis-operator`
14
+
👉 **[Migration Guide: CIS Benchmark to Rancher Compliance](https://support.scc.suse.com/s/kb/Migrating-from-Rancher-CIS-Benchmark-to-Rancher-Compliance?language=en_US)**
16
15
16
+
---
17
+
18
+
## Support Status
19
+
20
+
| Branch | Rancher Version | Status | Recommended Action |
21
+
| :--- | :--- | :--- | :--- |
22
+
|**main**| v2.11.x |**Security Only**| Move to [Compliance Operator](https://github.com/rancher/compliance-operator)|
23
+
|**release/v1.4**| v2.11.x |**Security Only**| Plan migration for Rancher 2.12+ |
24
+
|**release/v1.3**| v2.10.x |**Security Only**| Plan migration for Rancher 2.12+ |
25
+
|**release/v1.2**| v2.9.x |**EOL**| Upgrade to supported version |
26
+
27
+
### Maintenance Policy
28
+
***Issues & Feedback:** Direct all new feature requests or general bugs to the [Compliance Operator Issues](https://github.com/rancher/compliance-operator/issues).
29
+
***Security Patches:** We will continue to review PRs for documented security vulnerabilities (CVEs) on supported 2.10/2.11 lines. All other PRs will be redirected.
30
+
31
+
---
17
32
18
33
## Branches and Releases
19
34
### General information
@@ -38,11 +53,6 @@ bug fixes and security-related dependency bumps.
38
53
Refer to the [Support Compatibility Matrix](https://www.suse.com/suse-rancher/support-matrix/)
39
54
for official compatibility information.
40
55
41
-
### How future release branches should be generated
42
-
Follow these guidelines when releasing new branches:
43
-
1. Name convention to be used: `release/v1.x.x`.
44
-
2. Update the [Branch and Releases](https://github.com/rancher/cis-operator#branches-and-releases) table with the new branches and remove the no longer needed branches.
0 commit comments