Understand installation requirements

Getvisibility products use Kubernetes under the hood, and we have very specific hardware requirements. It's crucial to meet the minimum resource requirements defined for containers, as failing to do so can lead to various problems:

1. Resource Starvation: If a container requests more CPU or memory resources than are actually available on the cluster, it can lead to resource starvation. This means other containers may not get the resources they need to run correctly, causing performance degradation or even crashes.

2. Throttling: Kubernetes imposes resource limits for containers, and if a container's requested resources exceed its limits, Kubernetes may throttle or terminate the container to prevent it from consuming excessive resources, resulting in performance degradation.

3. Out of Memory or CrashLoopBackOff Errors: Oversubscribing memory resources can lead to containers running out of memory, causing them to terminate abruptly or enter a constant restart loop, commonly referred to as a "CrashLoopBackOff" error.

4. Performance Degradation: When requested CPU resources are larger than allocated, it can lead to performance issues as containers compete for CPU time, potentially slowing down critical processes and making the application unresponsive.

5. Difficult Troubleshooting: Misallocation of resources, whether it's too little or too much, can be challenging to identify and correct. This can lead to extended troubleshooting efforts and downtime as administrators attempt to resolve resource-related issues.

To ensure a stable and efficient Kubernetes deployment of our product, it's essential to accurately configure resource requests and limits for containers based on their actual requirements. This prevents resource-related problems and ensures smooth operation within the Kubernetes cluster.