Noe Alternatives

Similar projects and alternatives to noe based on common topics and language

buildah

25 7,003 9.6 Go noe VS buildah

A tool that facilitates building OCI images.
k8s-image-swapper

4 469 9.0 Go noe VS k8s-image-swapper

Mirror images into your own registry and swap image references automatically.
InfluxDB

www.influxdata.com featured

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
sample-mutatingwebhook

3 16 0.0 Go noe VS sample-mutatingwebhook

Kubernetes Mutating webhook sample example
bank-vaults

10 0 0.0 Go noe VS bank-vaults

Discontinued A Vault swiss-army knife: A CLI tool to init, unseal and configure Vault (auth methods, secret engines).
osm-edge

5 38 6.3 Go noe VS osm-edge

Discontinued osm-edge is a lightweight service mesh for the edge-computing. It's forked from openservicemesh/osm and use pipy as sidecar proxy.
problemsolver

1 3 5.8 Dockerfile noe VS problemsolver

An opiniated Docker image for troubleshooting purposes, especially within a Kubernetes cluster.
grype

56 7,649 9.5 Go noe VS grype

A vulnerability scanner for container images and filesystems
SaaSHub

www.saashub.com featured

SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better noe alternative or higher similarity.

Suggest an alternative to noe

noe reviews and mentions

Posts with mentions or reviews of noe. We have used some of these posts to build our list of alternatives and similar projects.

Show HN: Noe, a mutating webhook to make multi-arch simpler in Kubernetes
1 project | news.ycombinator.com | 6 Jun 2023

Hi folks!
Our team provides a multi-cluster, multi-region, multi-tenant, Kubernetes cluster as a service to the rest of the company [1].
Recently, we worked on adding ARM-nodes support and we found out that people usually rely on annotations to get the job done. Then, we realized that this is double work. You need to:
1. Build the image for multi-architecture
2. Annotate your deployment with the correct architecture
Isn't there a better way? So, Noe was born. Noe is a Kubernetes mutating webhook that dynamically assigns node architectures to match the requirements of container images within a Pod. It simplifies mixed-architecture deployments (e.g. ARM and x86) by ensuring that Pods are scheduled on nodes capable of executing all their images.
You can see more in the Github project.
1 - https://www.adevinta.com/
2 - https://github.com/adevinta/noe