Automate Kubernetes Network Policies With Otterize Intents?

  Рет қаралды 2,840

DevOps Toolkit

Жыл бұрын

Otterize Intents provide automation of Kubernetes network policies, Kafka ACLs, mTLS, and certificates with a focus on developers.
#kubernetesnetworking #kubernetes #otterize #k8s
Consider joining the channel: kzbin.infojoin
▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬
➡ Gist with the commands: gist.github.com/vfarcic/82f27dc7f8bde2708db9e5c5dec8e60b
🔗 Otterize: otterize.com
🎬 Kubernetes Network Policies Explained: kzbin.info/www/bejne/Z2mpdnRrrb11fbs
🎬 Performance Testing - What? Why? How? When? (with Ddosify Examples): kzbin.info/www/bejne/d5m9ZIyJqcmUh9U
▬▬▬▬▬▬ 💰 Sponsoships 💰 ▬▬▬▬▬▬
If you are interested in sponsoring this channel, please use calendly.com/vfarcic/meet to book a timeslot that suits you, and we'll go over the details. Or feel free to contact me over Twitter or LinkedIn (see below).
▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬
➡ Twitter: vfarcic
➡ LinkedIn: www.linkedin.com/in/viktorfarcic/
▬▬▬▬▬▬ 🚀 Other Channels 🚀 ▬▬▬▬▬▬
🎤 Podcast: www.devopsparadox.com/
💬 Live streams: kzbin.info
▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬
00:00 Introduction to Otterize Intents for Kubernetes Network Policies
01:35 Zero-Trust Network Security With Kubernetes Network Policies
04:28 Internal-Trust Network Security With Kubernetes Network Policies
05:32 Network Policy Automation With Otterize Intents
14:21 More From Otterize
14:53 Otterize Pros And Cons

Пікірлер: 4
@DevOpsToolkit
@DevOpsToolkit Жыл бұрын
What do you think about Otterize Intents? Does it help with management of Kubernetes network policies?
@SiCrip09
@SiCrip09 Жыл бұрын
When it comes to new tools it’s good to know what they can do and when a use case pops up you choose the best option 🚀
@dirien
@dirien Жыл бұрын
Nice tool but, as you stated, CNIs like Cilium offer with Hubble an already good way to visualise/create/manage Network Policies.
@TheTruthOfAI
@TheTruthOfAI Жыл бұрын
there is no way to scale and maintain this at large scale.. the best approach i guess "namespaced" approach.. u self-fence and self-service this.. im not keen on turning back into perimetrical itsec engineering just to firewall namespaces over thousands of pods and namespaces... truth is.. NSP around the industry are non-existent or weak as F... if i get inside 1 of ur pods... those NSP is not gonna save u from what is coming next :)