How to Enable Pod Presets
This document (000020125) is provided subject to the disclaimer at the end of this document.
Environment
Situation
Task
This how-to article outlines how to enable pod presets on your cluster. This is done by enabling the PodPreset
admission plugin and the settings.k8s.io/v1alpha1
API for the kube-apiserver.
Pre-requisites
- Kubernetes version 1.10 and above
- Access to edit the cluster in yaml or the cluster.yaml file you used with RKE.
Resolution
Get to the cluster yaml in Rancher by editing the cluster and selecting "edit as yaml" or opening the RKE cluster.yml file. Modify the kube-api section to resemble the following and hit save or run up
:
services:
kube-api:
extra_args:
runtime-config: authorization.k8s.io/v1beta1=true,settings.k8s.io/v1alpha1=true
enable-admission-plugins: PodPreset,NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize
Notice that settings.k8s.io/v1alpha1/podpreset
and PodPreset
are added to the runtime-config and admission plugins.
Further reading
More details can be found in the kubernetes docs on pod presets.
Status
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000020125
- Creation Date: 06-May-2021
- Modified Date:28-Mar-2024
-
- SUSE Rancher
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com