Krav means contact in Hebrew. Full contact k8s is an approach to k8s that focuses on practical real-world skills via the application of Krav Maga self-defense principles.
Krav Maga is a military self-defence and fighting system developed for the Israel Defense Forces (IDF) and Israeli security forces derived from a combination of techniques sourced from Boxing, Wrestling, Judo, Aikido, and Karate. Krav Maga is known for its focus on real-world situations and its extreme efficiency. It was derived from the street-fighting experience of Hungarian-Israeli martial artist Imi Lichtenfeld, who made use of his training as a boxer and wrestler, while defending the Jewish quarter against fascist groups in Bratislava, Czechoslovakia, during the mid-to-late 1930s. In the late 1940s, after his aliyah to Mandatory Palestine, he began to provide lessons on combat training to what was to become the IDF.
Krav Maga has a philosophy emphasizing aggression, and simultaneous defensive and offensive maneuvers.
Some of the key focus is instinctive response under stress. To that end, Krav Maga is an eclectic system that has not sought to replace existing effective techniques, taking what is useful from available systems, for example:
* Strikes – as per karate, and boxing,
* Take-downs and throws – per judo, aikido and wrestling
* Ground work – per judo and wrestling
* Escapes from chokes and holds – per judo, aikido, wrestling
* Empty-hand weapon defenses – per aikido
DevSecOps is an eccelctic system as well.
@mcgonagle DevSecOps Definition - Shifting Security Left through a Technical and Cultural Focus on Teamwork and the Secure Delivery of Software Mission.
The purpose of DevSecOps is to integrate security controls and processes into the DevOps software development cycle, a process which is achieved by promoting the collaboration between security teams, development teams and operations teams.
Kraverenetes is a practical DevSecOps methodology which focuses on the four pillars of Krav Maga, which are:
1. awareness
2. avoidance
3. de-escalation and escape
4. last-resort decisive, simultaneous attack and defense
1. Be aggressive but smart in your problem solving.
2. Be vigilant in identifing and addressing challenges.
3. Be proactive based on your current weaknesses or vulnerabilities; react quickly when you have to.
4. Be tool agnostic.
5. Invoke precision when executing tasks.
6. Employ simple and repeatable techniques.
7. Include situational awareness in all aspects of your practice.
8. Understand the impact of stress on your planning and response.
1. Be aggressive but smart in your problem solving
kubectl delete --force --grace-period=0 when pods are stuck, but understand the consequenceskubectl scale deployment/app --replicas=202. Be vigilant in identifying and addressing challenges
kubectl get events --watch --all-namespaces3. Be proactive based on your current weaknesses; react quickly when you have to
kube-bench and kubesec regularly to identify security gapskubectl rollout undo deployment/app4. Be tool agnostic
kubectl and alternative tools (k9s, lens, stern)5. Invoke precision when executing tasks
kubectl delete pods -l app=nginx,version=v1.2.36. Employ simple and repeatable techniques
7. Include situational awareness in all aspects of your practice
kubectl cluster-info and kubectl get nodeskubectl top nodes and kubectl top pods8. Understand the impact of stress on your planning and response
Retzev in Kravernetes means maintaining continuous, flowing operations that seamlessly combine defensive security measures with offensive optimization techniques. Like in Krav Maga, you never stop moving - each action flows into the next.
Continuous Motion Examples:
Security Scanning → Remediation → Validation:
# Flow from discovery to action
kube-bench run → kubectl apply -f security-policy.yaml → kubesec scan deployment.yaml
Monitoring → Alerting → Auto-scaling → Optimization:
# Metrics trigger scaling which triggers optimization
kubectl top nodes → HPA triggers → kubectl scale → Resource optimization
Deploy → Test → Monitor → Rollback/Forward:
# Deployment flows immediately into verification
kubectl apply -f app.yaml && kubectl rollout status deployment/app && curl health-check || kubectl rollout undo deployment/app
Incident Response Chain:
# Immediate response flows through investigation to resolution
kubectl describe pod → kubectl logs → kubectl exec -it → kubectl patch/delete
GitOps Continuous Flow:
Git commit → CI/CD pipeline → Deployment → Health checks → Prometheus metrics → Alert → Auto-remediation → Git commit
The key is never stopping - each Kubernetes action should trigger the next logical step in an unbroken chain of defensive and offensive operations.
Situation awareness in Kubernetes is the foundation for successful cluster operations and incident response. Like in combat situations, lacking awareness leads to critical failures, security breaches, and service outages.
Kubernetes Awareness Levels:
-6 Unaware: No monitoring, no alerts, deployments without resource limits
-5 Semi-Aware: Basic monitoring but no proactive alerting
kubectl get pods occasionally-3 Aware: Regular monitoring with basic alerts
kubectl top nodes/pods checks during business hours-2 Cautious: Proactive monitoring with comprehensive alerting
-1 Alert: Advanced observability with predictive capabilities
0 Prepared: Full spectrum awareness with automated response
T - Technical Threats
H - Human Threats
R - Resource Threats
E - Environmental Threats
A - Application Threats
T - Trust Threats
Technical Threats:
Human Threats:
Resource Threats:
Environmental Threats:
Application Threats:
Trust Threats: