Kubernetes Gateway API
Adopting Gateway API for cluster ingress: GatewayClass, Gateway and route resources, splitting responsibilities between platform and application teams, and choosing an implementation.

Kubernetes capabilities that need their own design and configuration work in a self-managed cluster.
Adopting Gateway API for cluster ingress: GatewayClass, Gateway and route resources, splitting responsibilities between platform and application teams, and choosing an implementation.
Segmenting cluster traffic with NetworkPolicy: choosing a network plugin that enforces it, default deny patterns, namespace and pod selectors, egress control and testing policies.
Configuring Kubernetes API audit logging: writing an audit policy, choosing levels per resource, log and webhook backends, retention flags and shipping audit events to a SIEM.
Scaling workloads and nodes in a self-managed cluster: HorizontalPodAutoscaler, the Vertical Pod Autoscaler add-on, in-place pod resizing, KEDA for event-driven scaling and node autoscaling.
Running GPU and accelerator workloads with Dynamic Resource Allocation: DeviceClass and ResourceClaim design, device sharing, how it differs from device plugins and its preemption limit.
Running Windows Server workloads in Kubernetes: supported Windows versions and runtimes, Linux control plane, HostProcess containers instead of privileged pods, and pod fields Windows does not support.
Enforcing cluster rules with CEL-based ValidatingAdmissionPolicy instead of webhooks: policies, bindings, parameters and rolling out with Warn and Audit before Deny.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.