sparrowci_web
intents-operator
sparrowci_web | intents-operator | |
---|---|---|
11 | 10 | |
1 | 278 | |
- | 1.8% | |
0.0 | 9.3 | |
over 1 year ago | 3 days ago | |
Raku | Go | |
- | 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.
sparrowci_web
-
Monthly 'Shameless Self Promotion' thread - 2023/02
I continue to build community around SparrowCI - https://ci.sparrowhub.io - flexible CI system with many languages support. Welcome in! We already have active uses , but we welcome 🤗 more.
-
But really, why is all CI/CD pipelines?
With SparrowCI you have a compromise of having yaml based structure and flexibility to use many programming languages for tasks, and tasks act as functions accepting and returning parameters accessible within other tasks. You can check more out at https://ci.sparrowhub.io/
-
Monthly 'Shameless Self Promotion' thread - 2023/01
Continue to build super flexible CICD framework - https://ci.sparrowhub.io , recently I’ve added self hosted deployment support that allows people to install the system on their infrastructure. Another interesting feature is gitea integration
-
Monthly 'Shameless Self Promotion' thread - 2022/12
Checkout more on https://ci.sparrowhub.io
-
Sunday Daily Thread: What's everyone working on this week?
Keep building my own free CI service extendable by many languages including Python, please check out Python examples here - https://github.com/melezhik/SparrowCI/tree/main/examples/python
-
Monthly 'Shameless Self Promotion' thread - 2022/11
Now officially support builds for Alpine Linux, Debian and Arch Linux containers - see examples at https://ci.sparrowhub.io
-
Streamline your GitHub Actions dependencies using Nix
For example, in SparrowCI pipeline this could be achieved by a simple Bash task:
- Building raku alpine package on vanilla Alpine Linux
-
SparkyCI update
For more sophisticated scenarios try out .sparkyci.yaml DSL
-
SparkyCI Update
For more sophisticated scenarios there is .sparkyci.yaml DSL that allows to install none Raku packages, external services and so on, an example is my fork of DBIish::Pool repo - https://github.com/melezhik/DBIish-Pool/blob/main/.sparkyci.yaml
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
What are some alternatives?
py-template - One-click GitHub Actions pipelines for Python!
kubelet-csr-approver - Kubernetes controller to enable automatic kubelet CSR validation after a series of (configurable) security checks
DBIish-Pool - DBIish Connection Pool
certify - :lock: Create private CA and Issue Certificates without hassle
PoC_CVEs - PoC_CVEs
network-mapper - Map Kubernetes traffic: in-cluster, to the Internet, and to AWS IAM and export as text, intents, or an image
featbit - A feature flags service written in .NET
argocd-example-apps - Example Apps to Demonstrate Argo CD
DictDataBase - A python NoSQL dictionary database, with concurrent access and ACID compliance
ziti - The parent project for OpenZiti. Here you will find the executables for a fully zero trust, application embedded, programmable network @OpenZiti
Universal-Kubernetes-Helm-Charts - Some universal helm charts used for deploying services onto Kubernetes. All-in-one best-practices
Lux - Lux is a command-line interface for controlling and monitoring Govee lighting, built in Go.