intents-operator
constellation
intents-operator | constellation | |
---|---|---|
10 | 31 | |
278 | 870 | |
1.8% | 1.6% | |
9.3 | 9.9 | |
4 days ago | 5 days ago | |
Go | Go | |
Apache License 2.0 | GNU Affero General Public License v3.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
constellation
-
Using "Confidential Computing" with Hetzner? (Intel SGX/TDX, AMD SEV/SNP)
A lot happening in Europe, Enclaive provides encrypting containers (GitHub), Edgeless Systems provides a whole encrypted k8s with constellation (GitHub), then there are other players like scontain and secustack.
-
Mögliche Lösungen zu selbstzerstörenden Umgebungen mit einem Trigger
Aber schau dir bspw mal https://github.com/edgelesssys/constellation an.
-
Where are you hosting your Managed Kubernetes and why?
Would smth. like https://github.com/edgelesssys/constellation be helpful for those cases?
-
Why is K8 an issue when compliances become important for enterprises (HIPAA)
Hey u/Aztreix, we've recently released an open-source Kubernetes distribution that keeps all data always encrypted and isolates your workloads from cloud infrastructure. This solves many compliance requirements, at least for European companies. Feel free to check it out: https://github.com/edgelesssys/constellation.
- What Is Confidential Kubernetes?
-
Germany Forces a Microsoft 365 Ban Due to Privacy Concerns
Maybe they should deploy it via Constellation https://github.com/edgelesssys/constellation
- Constellation: Confidential Kubernetes
-
Setting up a "confidential" GitLab🦊🔒
Easy! I recently posted about our open-source project Constellation. Constellation is the first confidential Kubernetes distribution. Think Rancher Kubernetes Engine (RKE) or RedHat OpenShift for confidential computing.
-
What about Zero Trust Infrastructure?
Therefore, having such verifiable infrastructure seems paramount for a zero trust architecture. Constellation (https://github.com/edgelesssys/constellation) for example leverages Confidential Computing hardware to provide a fully-verifiable Kubernetes cluster. (Disclaimer: I work on that project)
-
What's your take on Zero Trust for Kubernetes?
Constellation does this as well btw: https://github.com/edgelesssys/constellation Disclaimer, I work on the project.
What are some alternatives?
kubelet-csr-approver - Kubernetes controller to enable automatic kubelet CSR validation after a series of (configurable) security checks
pocketbase - Open Source realtime backend in 1 file
certify - :lock: Create private CA and Issue Certificates without hassle
kcl - KCL Programming Language (CNCF Sandbox Project). https://kcl-lang.io
network-mapper - Map Kubernetes traffic: in-cluster, to the Internet, and to AWS IAM and export as text, intents, or an image
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
argocd-example-apps - Example Apps to Demonstrate Argo CD
node_crunch - Allows to distribute computations across several nodes
ziti - The parent project for OpenZiti. Here you will find the executables for a fully zero trust, application embedded, programmable network @OpenZiti
Cromtit - Run Tomtit scenarios as cron jobs and more.
Lux - Lux is a command-line interface for controlling and monitoring Govee lighting, built in Go.
vscode-kcl - VS Code KCL Extension