Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PSP #4

Open
morriq opened this issue Dec 6, 2021 · 0 comments
Open

PSP #4

morriq opened this issue Dec 6, 2021 · 0 comments

Comments

@morriq
Copy link
Owner

morriq commented Dec 6, 2021

Based on https://rancher.com/docs/k3s/latest/en/security/hardening_guide/#podsecuritypolicies

PSP is documented, but reading about PSP in k8s documentation shows

FEATURE STATE: Kubernetes v1.21 [deprecated]

and suggests to use https://kubernetes.io/docs/concepts/security/pod-security-standards/

but for now it's not documented in k3s and deprecated PSP showed in k3s documentation has issues with ECK.

So to handle ECK in k3s I must learn PSP which is hard to learn and deprecated.

That's why I don't put any PSP to ansible, you can do it on your own. Useful links:

https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-network-policies.html
elastic/cloud-on-k8s#2817
elastic/cloud-on-k8s#2108

Making PSP is not valid without

        k3s_server:
          etcd-snapshot-schedule-cron: '0 */6 * * *'
          etcd-s3-region: 'eu-central-1'
          etcd-s3-bucket: '{{s3_bucket}}'
          etcd-s3-access-key: '{{s3_access_key}}'
          etcd-s3-secret-key: '{{s3_secret_key}}'
          etcd-s3: yes
          tls-san: '{{ansible_host}}'
          # this lines:
		  kube-apiserver-arg:
             - 'enable-admission-plugins=NodeRestriction,PodSecurityPolicy,ServiceAccount'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant