Intents-operator Alternatives

intents-operator reviews and mentions

• Otterize launches open-source, declarative IAM permissions for workloads on AWS EKS clusters
  3 projects | dev.to | 10 Jan 2024

  No more! The open-source intents-operator and credentials-operator enable you to achieve the same, except without all that work: do it all from Kubernetes, declaratively, and just-in-time, through the magic of IBAC (intent-based access control).

• Alternative to Network Policys
  2 projects | /r/kubernetes | 2 Feb 2023

  As you've mentioned, it is not possible to define deny rules using the native NetworkPolicy resource. Instead, you could use your CNI’s implementation for network policies. If you use Calico as your CNI you can use Calico's network policies to create deny rules. You can also take a look at Otterize OSS, an open-source solution my team and I are working on recently. It simplifies network policies by defining them from the client’s perspective in a ClientIntents resource. You can use the network mapper to auto-generate those ClientIntents from the traffic in your cluster, and then deploy them and let the intents-operator manage the network policies for you.

• Did I miss something here, regarding network policies and helm templates? (Slightly ranty)
  3 projects | /r/kubernetes | 30 Jan 2023

  However, if you want to control pod-to-pod communication, you might be better suited with managing network policies using ClientIntents, which let you specify which pods should communicate with which, from the client's point of view, and without requiring labels beforehand. It's open source, have a look at the intents operator here: https://github.com/otterize/intents-operator

• Can I create a NetworkPolicy with podSelector that matches a pod name instead of its labels?
  1 project | /r/kubernetes | 9 Dec 2022

  You can try it out by installing an open source, standalone Kubernetes operator that implements them using network policies - https://github.com/otterize/intents-operator

• Monthly 'Shameless Self Promotion' thread - 2022/12
  8 projects | /r/devops | 2 Dec 2022

  Hi! I'm Tomer, the CEO of Otterize - a cloud-native open-source tool that makes secure access transparent for developers with a declarative approach to service-to-service authorization. Otterize allows you to automate the creation of network policies and Kafka ACLs in a Kubernetes cluster using a human-readable format. Just declare which services your code intends to call using a Kubernetes custom resource, and access will be granted automatically while blocking anything else. Give it a try! It's free and takes 5 min to get started. https://github.com/otterize/intents-operator

• Creating network policies for pods with services
  1 project | /r/kubernetes | 22 Nov 2022

  You can use https://github.com/otterize/intents-operator to easily configure network policies using only pod names by specifying logical connections (a->b, c->b), and the operator configures network policies and labels for cluster resources automatically.

• otterize/intents-operator: Manage network policies and Kafka ACLs in a Kubernetes cluster with ease.
  1 project | /r/devopsish | 17 Nov 2022
• Show HN: Intents Operator, turns dev intent into K8s netpolicies and Kafka ACLs
  1 project | news.ycombinator.com | 16 Nov 2022
• What's your take on Zero Trust for Kubernetes?
  3 projects | /r/kubernetes | 16 Nov 2022

  I'm very passionate about this as I think cybersecurity and ops people lean too far into control -- controlling people, that is, not just programs, and they end up shooting themselves in the foot. Instead, I think you should make it easy for devs in your team to create the right access controls, and that this is the only way to achieve zero trust. Zero-trust inherently relies on all access being intentional and authorized, so if other engineers don't declare which access their code needs, it's impossible to achieve. There's an open source Kubernetes operator that aims to get this concept right with network policies and Kafka ACLs - make it easy for one person to declare which access is intentional and start rolling out zero trust using network policies, and have the access control policy live alongside the client code. Check it out at https://github.com/otterize/intents-operator. Full disclosure - I'm one of the contributors, so I'm a bit biased ;) I'm there on the Slack, so feel free to hit me up (Ori).

• Manage network policies and Kafka ACLs in a Kubernetes cluster with ease
  1 project | /r/kubernetes | 15 Nov 2022

  Hi all, I’m Tomer @Otterize. We just launched an open-source tool to easily automate the creation of network policies and Kafka ACLs in a Kubernetes cluster using a human-readable format, via a custom resource. Check it out - https://github.com/otterize/intents-operator

• A note from our sponsor - SaaSHub
  www.saashub.com | 3 Dec 2024

  SaaSHub helps you find the best software and product alternatives Learn more →