github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-21 10:51:29 +00:00
Code Issues Projects Releases Wiki Activity

fix alias for stack protector kernel config.

Browse Source 
- fix YAML syntax
- alias -> aliases
- no need for CONFIG prefix
- add renamed config since 4.18
This commit is contained in:
Jiahui Feng 2020-02-19 14:41:42 -08:00
parent afa72e93cd
commit 68b7564e7e
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
test/e2e_node/system/specs/gke.yaml
View File

@ -49,7 +49,7 @@ kernelSpec:
- name: IP6_NF_IPTABLES - name: IP6_NF_IPTABLES
description: 'Required by kube-proxy.' description: 'Required by kube-proxy.'
- name: IP_NF_TARGET_REDIRECT - name: IP_NF_TARGET_REDIRECT
alias: aliases:
- NETFILTER_XT_TARGET_REDIRECT - NETFILTER_XT_TARGET_REDIRECT
description: 'Enabled REDIRECT: all incoming connections are mapped onto description: 'Enabled REDIRECT: all incoming connections are mapped onto
the incoming interface''s address, causing the packets to come to the the incoming interface''s address, causing the packets to come to the
@ -167,10 +167,11 @@ kernelSpec:
description: 'Enabled the SECCOMP application API.' description: 'Enabled the SECCOMP application API.'
- name: SECURITY_APPARMOR - name: SECURITY_APPARMOR
description: 'Enable for AppArmor support.' description: 'Enable for AppArmor support.'
- name: CC_STACKPROTECTOR_STRONG - name: CC_STACKPROTECTOR_STRONG # Linux kernel <= 4.17
alias: aliases:
- CONFIG_CC_STACKPROTECTOR_REGULAR - CC_STACKPROTECTOR_REGULAR # Linux kernel <= 4.17
CONFIG_CC_STACKPROTECTOR_ALL - CC_STACKPROTECTOR_ALL # Linux kernel <= 4.17
- STACKPROTECTOR_STRONG # Linux kernel >= 4.18
description: 'Add the stack buffer overflow protections.' description: 'Add the stack buffer overflow protections.'
- name: STRICT_DEVMEM - name: STRICT_DEVMEM
description: 'Required for blocking the direct physical memory access.' description: 'Required for blocking the direct physical memory access.'