We shall create a set of sample custom sizing configmaps that do not allow users to modify the detailed resource settings within these configmaps. This means all the resources settings in these configmaps are fixed values or OOTB.
The reason for this is that, user will use some tooling to input load factors such as number of transactions per second which will gear the tooling to generate such configmaps. Once these configmaps submitted to git repo, the GitOps process will consume and sync onto target system.
As example, we could have:
.
└── config
└── cp4waiops (cp4waiops gitops configuration)
└── custom-sizing (cp4waiops custom sizing sample configuration)
├── templates
│ ├──custom-sizing-configmap.yaml (configmap for arbitrary user input)
│ ├──custom-sizing-resource-lockers.yaml(custom sizing not covered by configmap for arbitrary user input)
│ ├──x-small-configmap.yaml (configmap for general x-small)
│ ├──x-small-idle-configmap.yaml (configmap specific for idle workload using x-small)
│ ├──x-small-lad-configmap.yaml (configmap specific for lad use case using x-small)
│ ├──x-small-mad-configmap.yaml (configmap specific for mad use case using x-small)
│ ├──x-small-resource-lockers.yaml (custom sizing not covered by configmap for general x-small)
│ ├──x-small-idle-resource-lockers.yaml (custom sizing not covered by configmap for idle workload using x-small)
│ ├──x-small-lad-resource-lockers.yaml (custom sizing not covered by configmap for lad using x-small)
│ ├──x-small-mad-resource-lockers.yaml (custom sizing not covered by configmap for mad using x-small)
│ ├──small-lad-configmap.yaml (configmap specific for lad use case using small)
│ ├──small-mad-configmap.yaml (configmap specific for mad use case using small)
│ ├──small-lad-resource-lockers.yaml (custom sizing not covered by configmap for lad using small)
│ └──small-mad-resource-lockers.yaml (custom sizing not covered by configmap for mad using small)
└── values.yaml (values for arbitrary user input, and the profile, e.g.: x-small, x-small-idle, x-small-lad, small-mad, etc.)
We shall create a set of sample custom sizing configmaps that do not allow users to modify the detailed resource settings within these configmaps. This means all the resources settings in these configmaps are fixed values or OOTB.
The reason for this is that, user will use some tooling to input load factors such as number of transactions per second which will gear the tooling to generate such configmaps. Once these configmaps submitted to git repo, the GitOps process will consume and sync onto target system.
As example, we could have: