The objective of this page is to investigate Prometheus operators to achieve following: Understanding Prometheus Operator architecture. Prometheus configuration to collect custom metrics from applications running on different namespace. Custom metric configuration should be achieved by non-admin user in own namespace, not where Prometheus is deployed. Custom metric collection from…

Introduction The placement constraints in K8s clusters for POD/Job scheduling can be achieved by assigning node labeling directly on kubernetes cluster via kubectl. The created label can be used in kubernetes deployment as node selector. The presence of node selector determines , the resources scheduling on desired host/hardware. Demonstration The…

Introduction Multi tenancy on k8s cluster can be achieved using Namespace and RBAC approach. A multi-tenant cluster is shared by multiple users and/or workloads which are referred to as “tenants”. The operators of multi-tenant clusters must isolate tenants from each other to minimize the damage that a compromised or malicious…

1. Introduction Kubernetes does not offer an implementation of network load-balancers for bare metal clusters. In that case, bare metal cluster operators are left with two solution: “NodePort” and “externalIPs” services. Both of these options has significant limitation for production workload. Kubernetes does ship with all glue code that calls out to…