ipfs-cluster
cert-manager
ipfs-cluster | cert-manager | |
---|---|---|
14 | 101 | |
1,454 | 11,486 | |
0.7% | 1.1% | |
8.2 | 9.8 | |
7 days ago | 4 days ago | |
Go | Go | |
GNU General Public License v3.0 or later | 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.
ipfs-cluster
- BTFS (BitTorrent Filesystem)
-
Blockchain : Création de réseaux privés décentralisés avec EdgeVPN et application à l’opérateur…
IPFS Cluster
-
Reminder: Libgen is also hosted on the IPFS network here, which is decentralized and therefore much harder to take down
As Libgen is an ever-expanding collection wouldn't something like IPFS Cluster fit this a lot better?
- Why the Internet Needs the InterPlanetary File System
-
Fast way to sync ipfs datastores across computers?
There's also IPFS-cluster if you're into those features.
-
Has anyone successfully migrated their content off pinata and onto a self hosted ipfs server?
Then from there, it should be however connectable your server is. If you run multiple, there's ipfs-cluster as an option to sync them. Most of the time I simply send a CID list over ssh.
-
How do I "USE" IPFS Cluster?
The cluster as in https://cluster.ipfs.io/ would control the pinning of data. afaik the control would be private, like what it pins. The docs have a space for a key which I assume controls it.
-
Help Preserve the Internet with Archiveteam's Warrior
AFAIK you can use IPFS (& clusters[0]) without relying on the crypto parts of that ecosystem. That ought to fit rather well with the use case.
[0] https://cluster.ipfs.io/
-
Private Pining Service for Public use
Sounds like a job for IPFS Cluster.
-
Storing Off-Chain data using NFT.Storage
Notably, NFT.Storage includes both long-term "cold storage" in the decentralized Filecoin network, as well as "hot storage" using IPFS Cluster.
cert-manager
-
deploying a minio service to kubernetes
cert-manager
-
Upgrading Hundreds of Kubernetes Clusters
The second one is a combination of tools: External DNS, cert-manager, and NGINX ingress. Using these as a stack, you can quickly deploy an application, making it available through a DNS with a TLS without much effort via simple annotations. When I first discovered External DNS, I was amazed at its quality.
-
Run WebAssembly on DigitalOcean Kubernetes with SpinKube - In 4 Easy Steps
On top of its core components, SpinKube depends on cert-manager. cert-Manager is responsible for provisioning and managing TLS certificates that are used by the admission webhook system of the Spin Operator. Let’s install cert-manager and KWasm using the commands shown here:
-
Importing kubernetes manifests with terraform for cert-manager
terraform { required_providers { kubectl = { source = "gavinbunney/kubectl" version = "1.14.0" } } } # The reference to the current project or a AWS project data "google_client_config" "provider" {} # The reference to the current cluster or EKS data "google_container_cluster" "my_cluster" { name = var.cluster_name location = var.cluster_location } # We configure the kubectl provider to use those values for authenticating provider "kubectl" { host = data.google_container_cluster.my_cluster.endpoint token = data.google_client_config.provider.access_token cluster_ca_certificate = base64decode(data.google_container_cluster.my_cluster.master_auth[0].cluster_ca_certificate) } #Download the multiple manifests file. data "http" "cert_manager_crds" { url = "https://github.com/cert-manager/cert-manager/releases/download/v${var.cert_manager_version}/cert-manager.crds.yaml" } data "kubectl_file_documents" "cert_manager_crds" { content = data.http.cert_manager_crds.response_body lifecycle { precondition { condition = 200 == data.http.cert_manager_crds.status_code error_message = "Status code invalid" } } } # We use the for_each or else this kubectl_manifest will only import the first manifest in the file. resource "kubectl_manifest" "cert_manager_crds" { for_each = data.kubectl_file_documents.cert_manager_crds.manifests yaml_body = each.value }
-
An opinionated template for deploying a single k3s cluster with Ansible backed by Flux, SOPS, GitHub Actions, Renovate, Cilium, Cloudflare and more!
SSL certificates thanks to Cloudflare and cert-manager
-
Deploy Rancher on AWS EKS using Terraform & Helm Charts
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/${CERT_MANAGER_VERSION}/cert-manager.crds.yaml
-
Setup/Design internal PKI
put the Sub-CA inside hashicorp vault to be used for automatic signing of services like https://cert-manager.io/ inside our k8s clusters.
-
Task vs Make - Final Thoughts
install-cert-manager: desc: Install cert-manager deps: - init-cluster cmds: - kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/{{.CERT_MANAGER_VERSION}}/cert-manager.yaml - echo "Waiting for cert-manager to be ready" && sleep 25 status: - kubectl -n cert-manager get pods | grep Running | wc -l | grep -q 3
-
Easy HTTPS for your private networks
I've been pretty frustrated with how private CAs are supported. Your private root CA can be maliciously used to MITM every domain on the Internet, even though you intend to use it for only a couple domain names. Most people forget to set Name Constraints when they create these and many helper tools lack support [1][2]. Worse, browser support for Name Constraints has been slow [3] and support isn't well tracked [4]. Public CAs give you certificate transparency and you can subscribe to events to detect mis-issuance. Some hosted private CAs like AWS's offer logs [5], but DIY setups don't.
Even still, there are a lot of folks happily using private CAs, they aren't the target audience for this initial release.
[1] https://github.com/FiloSottile/mkcert/issues/302
[2] https://github.com/cert-manager/cert-manager/issues/3655
[3] https://alexsci.com/blog/name-non-constraint/
[4] https://github.com/Netflix/bettertls/issues/19
[5] https://docs.aws.amazon.com/privateca/latest/userguide/secur...
-
☸️ Managed Kubernetes : Our dev is on AWS, our prod is on OVH
the Cert Manager
What are some alternatives?
gun - An open source cybersecurity protocol for syncing decentralized graph data.
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
ipfs - Peer-to-peer hypermedia protocol
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
dqlite - Embeddable, replicated and fault-tolerant SQL engine.
Portainer - Making Docker and Kubernetes management easy.
ipfs-cluster-webui - A webui for ipfs-cluster-service
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖
Sandstorm - Sandstorm is a self-hostable web productivity suite. It's implemented as a security-hardened web app package manager.
k3s - Lightweight Kubernetes
public-gateway-checker - Checks which public gateways are online or not
oauth2-proxy - A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.