CIS Benchmark #1

davidnuzik · 2020-04-08T22:10:56Z

We will need to create a unique set of benchmarks for RKE2.
The hardening guide effort is tracked in #84

davidnuzik · 2020-06-03T23:39:36Z

Bumping out of alpha milestone into beta.

davidnuzik · 2020-07-14T16:28:21Z

I separated out a separate issue for the CIS Hardening Guide into #84

davidnuzik · 2020-07-17T18:57:32Z

@ShylajaDevadiga let's sync on this issue in our next sync meeting.
This should pass kubebench with cis 1.5 profile to validate and close this out.

davidnuzik · 2020-07-27T16:10:25Z

I think we are just waiting on the fork to test with. When it's ready we can test.

briandowns · 2020-07-27T16:11:36Z

There were some changes since I last looked at it. Hoping it'll be ready today.

ShylajaDevadiga · 2020-07-29T16:45:14Z

CIS benchmark results from upstream:
Environment: RHEL 7.8, 3 master, 1 agent cluster
Result:

./kube-bench master --benchmark cis-1.5
[INFO] 1 Master Node Security Configuration
[INFO] 1.1 Master Node Configuration Files
[FAIL] 1.1.1 Ensure that the API server pod specification file permissions are set to 644 or more restrictive (Scored)
[FAIL] 1.1.2 Ensure that the API server pod specification file ownership is set to root:root (Scored)
[FAIL] 1.1.3 Ensure that the controller manager pod specification file permissions are set to 644 or more restrictive (Scored)
[FAIL] 1.1.4 Ensure that the controller manager pod specification file ownership is set to root:root (Scored)
[FAIL] 1.1.5 Ensure that the scheduler pod specification file permissions are set to 644 or more restrictive (Scored)
[FAIL] 1.1.6 Ensure that the scheduler pod specification file ownership is set to root:root (Scored)
[FAIL] 1.1.7 Ensure that the etcd pod specification file permissions are set to 644 or more restrictive (Scored)
[FAIL] 1.1.8 Ensure that the etcd pod specification file ownership is set to root:root (Scored)
[WARN] 1.1.9 Ensure that the Container Network Interface file permissions are set to 644 or more restrictive (Not Scored)
[WARN] 1.1.10 Ensure that the Container Network Interface file ownership is set to root:root (Not Scored)
[FAIL] 1.1.11 Ensure that the etcd data directory permissions are set to 700 or more restrictive (Scored)
[FAIL] 1.1.12 Ensure that the etcd data directory ownership is set to etcd:etcd (Scored)
[FAIL] 1.1.13 Ensure that the admin.conf file permissions are set to 644 or more restrictive (Scored)
[FAIL] 1.1.14 Ensure that the admin.conf file ownership is set to root:root (Scored)
[FAIL] 1.1.15 Ensure that the scheduler.conf file permissions are set to 644 or more restrictive (Scored)
[FAIL] 1.1.16 Ensure that the scheduler.conf file ownership is set to root:root (Scored)
[FAIL] 1.1.17 Ensure that the controller-manager.conf file permissions are set to 644 or more restrictive (Scored)
[FAIL] 1.1.18 Ensure that the controller-manager.conf file ownership is set to root:root (Scored)
[WARN] 1.1.19 Ensure that the Kubernetes PKI directory and file ownership is set to root:root (Scored)
[WARN] 1.1.20 Ensure that the Kubernetes PKI certificate file permissions are set to 644 or more restrictive (Scored)
[WARN] 1.1.21 Ensure that the Kubernetes PKI key file permissions are set to 600 (Scored)
[INFO] 1.2 API Server
[PASS] 1.2.1 Ensure that the --anonymous-auth argument is set to false (Not Scored)
[FAIL] 1.2.2 Ensure that the --basic-auth-file argument is not set (Scored)
[PASS] 1.2.3 Ensure that the --token-auth-file parameter is not set (Scored)
[PASS] 1.2.4 Ensure that the --kubelet-https argument is set to true (Scored)
[PASS] 1.2.5 Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate (Scored)
[PASS] 1.2.6 Ensure that the --kubelet-certificate-authority argument is set as appropriate (Scored)
[PASS] 1.2.7 Ensure that the --authorization-mode argument is not set to AlwaysAllow (Scored)
[PASS] 1.2.8 Ensure that the --authorization-mode argument includes Node (Scored)
[PASS] 1.2.9 Ensure that the --authorization-mode argument includes RBAC (Scored)
[WARN] 1.2.10 Ensure that the admission control plugin EventRateLimit is set (Not Scored)
[PASS] 1.2.11 Ensure that the admission control plugin AlwaysAdmit is not set (Scored)
[WARN] 1.2.12 Ensure that the admission control plugin AlwaysPullImages is set (Not Scored)
[WARN] 1.2.13 Ensure that the admission control plugin SecurityContextDeny is set if PodSecurityPolicy is not used (Not Scored)
[PASS] 1.2.14 Ensure that the admission control plugin ServiceAccount is set (Scored)
[PASS] 1.2.15 Ensure that the admission control plugin NamespaceLifecycle is set (Scored)
[FAIL] 1.2.16 Ensure that the admission control plugin PodSecurityPolicy is set (Scored)
[PASS] 1.2.17 Ensure that the admission control plugin NodeRestriction is set (Scored)
[PASS] 1.2.18 Ensure that the --insecure-bind-address argument is not set (Scored)
[PASS] 1.2.19 Ensure that the --insecure-port argument is set to 0 (Scored)
[PASS] 1.2.20 Ensure that the --secure-port argument is not set to 0 (Scored)
[PASS] 1.2.21 Ensure that the --profiling argument is set to false (Scored)
[PASS] 1.2.22 Ensure that the --audit-log-path argument is set (Scored)
[FAIL] 1.2.23 Ensure that the --audit-log-maxage argument is set to 30 or as appropriate (Scored)
[FAIL] 1.2.24 Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate (Scored)
[PASS] 1.2.25 Ensure that the --audit-log-maxsize argument is set to 100 or as appropriate (Scored)
[PASS] 1.2.26 Ensure that the --request-timeout argument is set as appropriate (Scored)
[PASS] 1.2.27 Ensure that the --service-account-lookup argument is set to true (Scored)
[PASS] 1.2.28 Ensure that the --service-account-key-file argument is set as appropriate (Scored)
[PASS] 1.2.29 Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate (Scored)
[PASS] 1.2.30 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Scored)
[PASS] 1.2.31 Ensure that the --client-ca-file argument is set as appropriate (Scored)
[PASS] 1.2.32 Ensure that the --etcd-cafile argument is set as appropriate (Scored)
[PASS] 1.2.33 Ensure that the --encryption-provider-config argument is set as appropriate (Scored)
[WARN] 1.2.34 Ensure that encryption providers are appropriately configured (Scored)
[WARN] 1.2.35 Ensure that the API Server only makes use of Strong Cryptographic Ciphers (Not Scored)
[INFO] 1.3 Controller Manager
[PASS] 1.3.1 Ensure that the --terminated-pod-gc-threshold argument is set as appropriate (Scored)
[PASS] 1.3.2 Ensure that the --profiling argument is set to false (Scored)
[PASS] 1.3.3 Ensure that the --use-service-account-credentials argument is set to true (Scored)
[PASS] 1.3.4 Ensure that the --service-account-private-key-file argument is set as appropriate (Scored)
[PASS] 1.3.5 Ensure that the --root-ca-file argument is set as appropriate (Scored)
[FAIL] 1.3.6 Ensure that the RotateKubeletServerCertificate argument is set to true (Scored)
[PASS] 1.3.7 Ensure that the --bind-address argument is set to 127.0.0.1 (Scored)
[INFO] 1.4 Scheduler
[PASS] 1.4.1 Ensure that the --profiling argument is set to false (Scored)
[PASS] 1.4.2 Ensure that the --bind-address argument is set to 127.0.0.1 (Scored)

== Remediations ==
1.1.1 Run the below command (based on the file location on your system) on the
master node.
For example, chmod 644 /etc/kubernetes/manifests/kube-apiserver.yaml

1.1.2 Run the below command (based on the file location on your system) on the master node.
For example,
chown root:root /etc/kubernetes/manifests/kube-apiserver.yaml

1.1.3 Run the below command (based on the file location on your system) on the master node.
For example,
chmod 644 /etc/kubernetes/manifests/kube-controller-manager.yaml

1.1.4 Run the below command (based on the file location on your system) on the master node.
For example,
chown root:root /etc/kubernetes/manifests/kube-controller-manager.yaml

1.1.5 Run the below command (based on the file location on your system) on the master node.
For example,
chmod 644 /etc/kubernetes/manifests/kube-scheduler.yaml

1.1.6 Run the below command (based on the file location on your system) on the master node.
For example,
chown root:root /etc/kubernetes/manifests/kube-scheduler.yaml

1.1.7 Run the below command (based on the file location on your system) on the master node.
For example,
chmod 644 /etc/kubernetes/manifests/etcd.yaml

1.1.8 Run the below command (based on the file location on your system) on the master node.
For example,
chown root:root /etc/kubernetes/manifests/etcd.yaml

1.1.9 Run the below command (based on the file location on your system) on the master node.
For example,
chmod 644 <path/to/cni/files>

1.1.10 Run the below command (based on the file location on your system) on the master node.
For example,
chown root:root <path/to/cni/files>

1.1.11 On the etcd server node, get the etcd data directory, passed as an argument --data-dir,
from the below command:
ps -ef | grep etcd
Run the below command (based on the etcd data directory found above). For example,
chmod 700 /var/lib/etcd

1.1.12 On the etcd server node, get the etcd data directory, passed as an argument --data-dir,
from the below command:
ps -ef | grep etcd
Run the below command (based on the etcd data directory found above).
For example, chown etcd:etcd /var/lib/etcd

1.1.13 Run the below command (based on the file location on your system) on the master node.
For example,
chmod 644 /etc/kubernetes/admin.conf

1.1.14 Run the below command (based on the file location on your system) on the master node.
For example,
chown root:root /etc/kubernetes/admin.conf

1.1.15 Run the below command (based on the file location on your system) on the master node.
For example,
chmod 644 /etc/kubernetes/scheduler.conf

1.1.16 Run the below command (based on the file location on your system) on the master node.
For example,
chown root:root /etc/kubernetes/scheduler.conf

1.1.17 Run the below command (based on the file location on your system) on the master node.
For example,
chmod 644 /etc/kubernetes/controller-manager.conf

1.1.18 Run the below command (based on the file location on your system) on the master node.
For example,
chown root:root /etc/kubernetes/controller-manager.conf

1.1.19 Run the below command (based on the file location on your system) on the master node.
For example,
chown -R root:root /etc/kubernetes/pki/

1.1.20 Run the below command (based on the file location on your system) on the master node.
For example,
chmod -R 644 /etc/kubernetes/pki/*.crt

1.1.21 Run the below command (based on the file location on your system) on the master node.
For example,
chmod -R 600 /etc/kubernetes/pki/*.key

1.2.2 Follow the documentation and configure alternate mechanisms for authentication. Then,
edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml
on the master node and remove the --basic-auth-file=<filename> parameter.

1.2.10 Follow the Kubernetes documentation and set the desired limits in a configuration file.
Then, edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml
and set the below parameters.
--enable-admission-plugins=...,EventRateLimit,...
--admission-control-config-file=<path/to/configuration/file>

1.2.12 Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml
on the master node and set the --enable-admission-plugins parameter to include
AlwaysPullImages.
--enable-admission-plugins=...,AlwaysPullImages,...

1.2.13 Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml
on the master node and set the --enable-admission-plugins parameter to include
SecurityContextDeny, unless PodSecurityPolicy is already in place.
--enable-admission-plugins=...,SecurityContextDeny,...

1.2.16 Follow the documentation and create Pod Security Policy objects as per your environment.
Then, edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml
on the master node and set the --enable-admission-plugins parameter to a
value that includes PodSecurityPolicy:
--enable-admission-plugins=...,PodSecurityPolicy,...
Then restart the API Server.

1.2.23 Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml
on the master node and set the --audit-log-maxage parameter to 30 or as an appropriate number of days:
--audit-log-maxage=30

1.2.24 Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml
on the master node and set the --audit-log-maxbackup parameter to 10 or to an appropriate
value.
--audit-log-maxbackup=10

1.2.34 Follow the Kubernetes documentation and configure a EncryptionConfig file.
In this file, choose aescbc, kms or secretbox as the encryption provider.

1.2.35 Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml
on the master node and set the below parameter.
--tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256

1.3.6 Edit the Controller Manager pod specification file /etc/kubernetes/manifests/kube-controller-manager.yaml
on the master node and set the --feature-gates parameter to include RotateKubeletServerCertificate=true.
--feature-gates=RotateKubeletServerCertificate=true

== Summary ==
34 checks PASS
21 checks FAIL
10 checks WARN
0 checks INFO

 ./kube-bench node --benchmark cis-1.5
failed to load YAML or JSON from provided input "/bin/cat: /var/lib/kubelet/config.yaml: No such file or directory
": yaml: mapping values are not allowed in this context
failed to load YAML or JSON from provided input "/bin/cat: /var/lib/kubelet/config.yaml: No such file or directory
": yaml: mapping values are not allowed in this context
failed to load YAML or JSON from provided input "/bin/cat: /var/lib/kubelet/config.yaml: No such file or directory
": yaml: mapping values are not allowed in this context
failed to load YAML or JSON from provided input "/bin/cat: /var/lib/kubelet/config.yaml: No such file or directory
": yaml: mapping values are not allowed in this context
[INFO] 4 Worker Node Security Configuration
[INFO] 4.1 Worker Node Configuration Files
[FAIL] 4.1.1 Ensure that the kubelet service file permissions are set to 644 or more restrictive (Scored)
[FAIL] 4.1.2 Ensure that the kubelet service file ownership is set to root:root (Scored)
[FAIL] 4.1.3 Ensure that the proxy kubeconfig file permissions are set to 644 or more restrictive (Scored)
[FAIL] 4.1.4 Ensure that the proxy kubeconfig file ownership is set to root:root (Scored)
[FAIL] 4.1.5 Ensure that the kubelet.conf file permissions are set to 644 or more restrictive (Scored)
[FAIL] 4.1.6 Ensure that the kubelet.conf file ownership is set to root:root (Scored)
[PASS] 4.1.7 Ensure that the certificate authorities file permissions are set to 644 or more restrictive (Scored)
[PASS] 4.1.8 Ensure that the client certificate authorities file ownership is set to root:root (Scored)
[FAIL] 4.1.9 Ensure that the kubelet configuration file has permissions set to 644 or more restrictive (Scored)
[FAIL] 4.1.10 Ensure that the kubelet configuration file ownership is set to root:root (Scored)
[INFO] 4.2 Kubelet
[PASS] 4.2.1 Ensure that the --anonymous-auth argument is set to false (Scored)
[PASS] 4.2.2 Ensure that the --authorization-mode argument is not set to AlwaysAllow (Scored)
[PASS] 4.2.3 Ensure that the --client-ca-file argument is set as appropriate (Scored)
[PASS] 4.2.4 Ensure that the --read-only-port argument is set to 0 (Scored)
[PASS] 4.2.5 Ensure that the --streaming-connection-idle-timeout argument is not set to 0 (Scored)
[FAIL] 4.2.6 Ensure that the --protect-kernel-defaults argument is set to true (Scored)
[PASS] 4.2.7 Ensure that the --make-iptables-util-chains argument is set to true (Scored)
[WARN] 4.2.8 Ensure that the --hostname-override argument is not set (Not Scored)
[WARN] 4.2.9 Ensure that the --event-qps argument is set to 0 or a level which ensures appropriate event capture (Not Scored)
[PASS] 4.2.10 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Scored)
[PASS] 4.2.11 Ensure that the --rotate-certificates argument is not set to false (Scored)
[FAIL] 4.2.12 Ensure that the RotateKubeletServerCertificate argument is set to true (Scored)
[WARN] 4.2.13 Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers (Not Scored)

== Remediations ==
4.1.1 Run the below command (based on the file location on your system) on the each worker node.
For example,
chmod 644 /etc/systemd/system/kubelet.service.d/10-kubeadm.conf

4.1.2 Run the below command (based on the file location on your system) on the each worker node.
For example,
chown root:root /etc/systemd/system/kubelet.service.d/10-kubeadm.conf

4.1.3 Run the below command (based on the file location on your system) on the each worker node.
For example,
chmod 644 /etc/kubernetes/proxy.conf

4.1.4 Run the below command (based on the file location on your system) on the each worker node.
For example, chown root:root /etc/kubernetes/proxy.conf

4.1.5 Run the below command (based on the file location on your system) on the each worker node.
For example,
chmod 644 /etc/kubernetes/kubelet.conf

4.1.6 Run the below command (based on the file location on your system) on the each worker node.
For example,
chown root:root /etc/kubernetes/kubelet.conf

4.1.9 Run the following command (using the config file location identified in the Audit step)
chmod 644 /var/lib/kubelet/config.yaml

4.1.10 Run the following command (using the config file location identified in the Audit step)
chown root:root /var/lib/kubelet/config.yaml

4.2.6 If using a Kubelet config file, edit the file to set protectKernelDefaults: true.
If using command line arguments, edit the kubelet service file
/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and
set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
--protect-kernel-defaults=true
Based on your system, restart the kubelet service. For example:
systemctl daemon-reload
systemctl restart kubelet.service

4.2.8 Edit the kubelet service file /etc/systemd/system/kubelet.service.d/10-kubeadm.conf
on each worker node and remove the --hostname-override argument from the
KUBELET_SYSTEM_PODS_ARGS variable.
Based on your system, restart the kubelet service. For example:
systemctl daemon-reload
systemctl restart kubelet.service

4.2.9 audit test did not run: failed to run: "/bin/cat /var/lib/kubelet/config.yaml", output: "/bin/cat: /var/lib/kubelet/config.yaml: No such file or directory\n", error: exit status 1

4.2.12 Edit the kubelet service file /etc/systemd/system/kubelet.service.d/10-kubeadm.conf
on each worker node and set the below parameter in KUBELET_CERTIFICATE_ARGS variable.
--feature-gates=RotateKubeletServerCertificate=true
Based on your system, restart the kubelet service. For example:
systemctl daemon-reload
systemctl restart kubelet.service

4.2.13 audit test did not run: failed to run: "/bin/cat /var/lib/kubelet/config.yaml", output: "/bin/cat: /var/lib/kubelet/config.yaml: No such file or directory\n", error: exit status 1


== Summary ==
10 checks PASS
10 checks FAIL
3 checks WARN
0 checks INFO

davidnuzik · 2020-07-31T19:07:35Z

I'm leaving this in working state to cover the final work to use rancher/security-scan (instead of upstream to kubebench).
Thus, @ShylajaDevadiga will standby until that is in. Once that is ready we should post an update here or link PR and then Shylaja can pick this back up.

davidnuzik added the kind/task Work not related to bug fixes or new functionality label Apr 16, 2020

davidnuzik added this to the initial milestone Apr 16, 2020

davidnuzik added the [zube]: Backlog label Apr 17, 2020

cjellick added [zube]: Next Up and removed [zube]: Backlog labels Apr 28, 2020

cjellick modified the milestones: Beta, Alpha Apr 28, 2020

davidnuzik assigned briandowns Jun 1, 2020

davidnuzik added [zube]: Working and removed [zube]: Next Up labels Jun 1, 2020

davidnuzik modified the milestones: Alpha, Beta Jun 3, 2020

davidnuzik mentioned this issue Jul 14, 2020

[Documentation] CIS Hardening Guide #84

Closed

davidnuzik changed the title ~~CIS Benchmark and Hardening Guide~~ CIS Benchmark Jul 14, 2020

davidnuzik added [zube]: To Test and removed [zube]: Working labels Jul 17, 2020

davidnuzik assigned ShylajaDevadiga Jul 17, 2020

davidnuzik added [zube]: Working and removed [zube]: To Test labels Jul 27, 2020

davidnuzik unassigned ShylajaDevadiga Jul 27, 2020

zube bot assigned ShylajaDevadiga Jul 27, 2020

davidnuzik mentioned this issue Jul 31, 2020

CIS Benchmark - Upstream kubebench profile #94

Closed

davidnuzik unassigned ShylajaDevadiga Aug 4, 2020

uchalasani mentioned this issue Mar 14, 2024

Pods starting on other nodes than labeled nodes for the namespace #5615

Closed

Mikrz mentioned this issue Mar 31, 2024

Unable to restore cluster from snapshot, Failed to validate golang version #5655

Closed

shindebshekhar mentioned this issue Apr 18, 2024

RKE2 upgrade from v1.27.10+rk2r1 to v1.28.8+rke2r1 fails #5800

Closed

Badrmoh mentioned this issue Apr 29, 2024

RKE2 kube-proxy livenessProbe probe fails when--healthz-bind-address set to 127.0.0.1 #5860

Closed

dirkdaems mentioned this issue Apr 29, 2024

Rancher keeps trying to provision additional nodes although OpenStack quota exceeded rancher/rancher#45292

Closed

xyzzyz mentioned this issue May 3, 2024

ServiceLB is broken when rke2-cloud-provider is on 1.29 but k8s version is <=1.28 #5882

Closed

R00tedSec mentioned this issue May 9, 2024

rke2-coredns stuck on containercreating, failed to create pod sandbox #5905

Closed

shindebshekhar mentioned this issue May 15, 2024

v1.26.13+rke2r1 and v1.27.10+rke2r1 rke2 on-demand snapshot fails if hostname is in uppercase #5913

Closed

agaxprex mentioned this issue May 17, 2024

RKE2 Airgap Install: containerd fails to create and run containers #5923

Closed

mhegreberg mentioned this issue May 20, 2024

pods can no longer reach network/internet #5929

Closed

pvreddy37 mentioned this issue May 24, 2024

Security Vulnerability: rancher/klipper-helm:v0.8.2-build20230815 uses docker/moby version:23.0.1+incompatible Which is Vulnerable #5993

Closed

mhegreberg mentioned this issue May 29, 2024

restrict pod<->pod traffic to a certain NIC on the host (Using Calico) #6060

Closed

joelcomp1 mentioned this issue Jun 11, 2024

Losing 2 nodes in 3 node cluster seems to take down the remaining node #6182

Closed

jbisinfor mentioned this issue Jul 11, 2024

RKE2 wont start on RHEL 9 on AWS #6306

Closed

shindebshekhar mentioned this issue Jul 25, 2024

CSI snapshot controller upgrade fails after upgrade to v1.29.6+rke2r1 #6413

Closed

aceeric mentioned this issue Aug 5, 2024

Use of data-dir does not place CLIs (e.g. kubectl) on the file system #6474

Closed

VestigeJ mentioned this issue Aug 8, 2024

SUC Upgrade is unable to complete on SLE Micro 6 #6519

Closed

xyzzyz mentioned this issue Aug 9, 2024

When using ServiceLB in CIS profile, only traffic coming on node external ip is reaching the ServiceLB service. #6528

Open

shindebshekhar mentioned this issue Aug 14, 2024

Helm Chart upgrade fails after upgrade from rke2 v1.28.8+rke2r1 to v1.29.6+rke2r1 #6568

Closed

mynktl mentioned this issue Aug 15, 2024

rke2 start fails after rke2-killall.sh execution #6571

Open

davidgaster mentioned this issue Aug 15, 2024

ServiceLB pods in Kube-System fail to deploy on v1.27.15 #6575

Closed

shindebshekhar mentioned this issue Aug 26, 2024

Calico Helm Chart upgrade fails after upgrade from rke2 v1.28.8+rke2r1 to v1.28.12+rke2r1 / v1.29.6+rke2r1 #6633

Open

dehoej mentioned this issue Aug 30, 2024

rke2 redeployed rke2-ingress-nginx with default config #6668

Closed

bluefish1976 mentioned this issue Sep 6, 2024

Air-Gap environment failed to pull images from insecure private registry #6759

Closed

agaxprex mentioned this issue Sep 16, 2024

Etcd is consistently crashing on RKE2 deployment #6824

Closed

cloudcafetech mentioned this issue Sep 26, 2024

Failed to get MemberList from server #6872

Closed

bpopovich44 mentioned this issue Oct 10, 2024

Unable to connect to the server: tls: failed to verify certificate: x509: certificate has expired or is not yet valid rancher/rancher#47498

Closed

cdmx1 mentioned this issue Oct 11, 2024

rke2-server failing to start #7011

Closed

ertanci mentioned this issue Oct 15, 2024

How does RKE2 limit pids in a container? #7041

Closed

frit0-rb mentioned this issue Oct 18, 2024

Disk IO queue (aqu-sq) is high. Disk saturation #7072

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

CIS Benchmark #1

CIS Benchmark #1

davidnuzik commented Apr 8, 2020 •

edited

Loading

davidnuzik commented Jun 3, 2020

davidnuzik commented Jul 14, 2020

davidnuzik commented Jul 17, 2020 •

edited

Loading

davidnuzik commented Jul 27, 2020

briandowns commented Jul 27, 2020

ShylajaDevadiga commented Jul 29, 2020 •

edited

Loading

davidnuzik commented Jul 31, 2020

CIS Benchmark #1

CIS Benchmark #1

Comments

davidnuzik commented Apr 8, 2020 • edited Loading

davidnuzik commented Jun 3, 2020

davidnuzik commented Jul 14, 2020

davidnuzik commented Jul 17, 2020 • edited Loading

davidnuzik commented Jul 27, 2020

briandowns commented Jul 27, 2020

ShylajaDevadiga commented Jul 29, 2020 • edited Loading

davidnuzik commented Jul 31, 2020

davidnuzik commented Apr 8, 2020 •

edited

Loading

davidnuzik commented Jul 17, 2020 •

edited

Loading

ShylajaDevadiga commented Jul 29, 2020 •

edited

Loading