You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Modify px-bench environment settings for the deployed storageclasses and newly created namespaces
Create a working version of a copy of the examples/generic/px-bench-env.yml file and customize it:
metadata.namespace: px-bench add to: ServiceAccount, ConfigMap, Role, RoleBinding, Job
storageclass_list: [quoted space-separated list of storageclasses to be used by benchmarks; e.g., "sc-01 sc-02"]
Customize px-bench-main.yml file:
metadata.namespace: px-bench add to: ConfigMap, Role, RoleBinding, Job
set runAsNonRoot: false for both fio and run containers: fio container: ConfigMap "files", run.sh, Job "fio", spec.template.spec.containers.securityContext run container: Job "run", spec.template.spec.containers.securityContext
As described in px-bench main README.md, apply chewram,yml, px-bench-env.yml, px-bench-main.yml and continue with post benchmarking monitoring and retrieval operations.
The text was updated successfully, but these errors were encountered:
TKGS Tanzu px-bench configuration recommendations
Overview
These are recommendations for deploying and testing with px-bench in a TKGS Tanzu cluster that supplement px-bench main README.md
Cluster environment prep
Create namespaces and rolebindings [if needed] for chewram and px-bench
kubectl create ns chewram
kubectl create rolebinding rolebinding-default-privileged-sa-ns_default --namespace=chewram --clusterrole=psp:vmware-system-privileged --group=system:serviceaccounts
kubectl create ns px-bench
kubectl create rolebinding rolebinding-default-privileged-sa-ns_default --namespace=px-bench --clusterrole=psp:vmware-system-privileged --group=system:serviceaccounts
Modify px-bench environment settings for the deployed storageclasses and newly created namespaces
Create a working version of a copy of the
examples/generic/px-bench-env.yml
file and customize it:metadata.namespace: px-bench
add to: ServiceAccount, ConfigMap, Role, RoleBinding, Jobstorageclass_list
: [quoted space-separated list of storageclasses to be used by benchmarks; e.g., "sc-01 sc-02"]Customize
px-bench-main.yml
file:metadata.namespace: px-bench
add to: ConfigMap, Role, RoleBinding, JobrunAsNonRoot: false
for bothfio
andrun
containers:fio
container: ConfigMap "files", run.sh, Job "fio",spec.template.spec.containers.securityContext
run
container: Job "run",spec.template.spec.containers.securityContext
As described in px-bench main README.md, apply
chewram,yml
,px-bench-env.yml
,px-bench-main.yml
and continue with post benchmarking monitoring and retrieval operations.The text was updated successfully, but these errors were encountered: