intents-operator
ziti
intents-operator | ziti | |
---|---|---|
10 | 84 | |
278 | 2,097 | |
1.8% | 11.4% | |
9.3 | 9.8 | |
4 days ago | 3 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
intents-operator
-
Otterize launches open-source, declarative IAM permissions for workloads on AWS EKS clusters
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
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)
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?
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
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
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.
- Show HN: Intents Operator, turns dev intent into K8s netpolicies and Kafka ACLs
-
What's your take on Zero Trust for Kubernetes?
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
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
ziti
- Show HN: OpenZiti (Apache 2.0, P2P, E2E encrypted, full mesh overlay) is now 1.0
-
Has anyone tried OpenZiti?
If you are not aware of what OpenZiti is, this is the description available on their website:
-
zrok: open-source peer-to-peer sharing (release of 0.4.0)
fwiw, its back up. stars for zrok and ziti (i.e., the parent repo) are super appreciated!
-
Self-Hosted Mesh Network / VPN For User-Friendly LAN Gaming Network?
https://github.com/openziti/ziti (1.2k stars)
-
K3S, Authentik, And Practical Use
Create an AUR package for the ziti binaries
-
Docker-Compose Woes
I ask because I'm going to start with the simplified-docker-compose.yml file instead of the more complicated one for starters
-
Upgrading VPN solutions in a remote working Environment
OpenZiti is the most sophisticated and simple-to-use ZTNA platform on the planet. Allows you to create micro-segmented ZTNA networks by desktop application, web application, device, containers, API, and servers. All data is distributed dynamically across an overlay mesh network focused on routing performance, self-healing, and latency. It has desktop clients on all operating systems, pre-built SSH consoles, and SDKs in different languages to integrate OpenZiti into any product natively. And best of all, it's Open-Source. Seriously, try it, you'll be mind-blowing...
-
An SDK for embedding zero trust networking into Node.JS applications and web servers to improve security.
This repo hosts the OpenZiti SDK for NodeJS, and is designed to help you deliver secure applications over a OpenZiti Network - https://github.com/openziti/ziti-sdk-nodejs.
- Ziti
-
Looking for a "file-ingress"/"file upload" service for arbitary person w/ one time link/email
zrok.io seems fit for this purpose though you'd have to do a little work like combining it with FileGator or similar. Future releases would add this functionality directly, you could just watch the project. It is fundamentally designed for web app & webhook testing. It's built on top of a zero-trust networking overlay technology called openziti.io. There are developer discourse channels to help.
What are some alternatives?
kubelet-csr-approver - Kubernetes controller to enable automatic kubelet CSR validation after a series of (configurable) security checks
oauth2-proxy - A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.
certify - :lock: Create private CA and Issue Certificates without hassle
tailscale - The easiest, most secure way to use WireGuard and 2FA.
network-mapper - Map Kubernetes traffic: in-cluster, to the Internet, and to AWS IAM and export as text, intents, or an image
ZeroTier - A Smart Ethernet Switch for Earth
argocd-example-apps - Example Apps to Demonstrate Argo CD
OPAL - Policy and data administration, distribution, and real-time updates on top of Policy Agents (OPA, Cedar, ...)
Lux - Lux is a command-line interface for controlling and monitoring Govee lighting, built in Go.
devtron - Tool integration platform for Kubernetes
pcreds - save ~20 seconds when copy/pasting to your aws credentials file from Control Tower
gdg - Grafana Dashboard Manager