Understanding the VMware Tanzu terminology - General Kubernetes reading including Pod Security Policy
Writing these things in retrospect is not a good idea at all! If you ever do one of these kinds of challenges or tasks. Note down your days even in short form, even if you can't publish straight away.
But luckily I have a lot of previous stuff to share aswell.
One of my most visited blog posts I've written up recently is breaking down the VMware Tanzu terminology, helping explain the differences in the portfolio and its features. You can find the link below.
Pod Security Policy is a pain in the backside. I know it's there for a reason, to increase the security posture of your cluster. But for my demo and tests I don't care. PSP is actuallly being deprecated in the future. I've posted some useful links below as well.
- Kubernetes Operators 101
- Understanding the VMware Tanzu Kubernetes Terminology
- Kubernetes Pod Security Policy Best Practices
- Example Role Bindings for Pod Security Policy
- How to Manage Kubernetes Pod Security Policy Deprecation
- Unofficial Kubernetes - Pod Security Policy
- Using Helm I needed to specify a particual storage class during a deployment. You can do this using:
helm install --name my-release --set persistence.storageClass=nfs-client,mariadb.master.persistence.storageClass=nfs-client stable/wordpress