kube-httpcache
kubernetes-replicator
| kube-httpcache | kubernetes-replicator | |
|---|---|---|
| 3 | 3 | |
| 290 | 815 | |
| 2.1% | 3.1% | |
| 7.2 | 6.2 | |
| 7 days ago | about 1 month ago | |
| Go | Go | |
| MIT License | 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.
kube-httpcache
- Simple HTTP response cache?
-
Need help trying to set up Varnish on Kubernetes using kube-httpcache. I managed to get it rolling but I am having problems regarding authentication and other problems that I have not encountered before. Any help and input would be appreciated.
Hi, I am trying to set up Varnish on Kubernetes and for that I am using kube-httpcache that allows me to dinamically chante the default.vcl config file without much hassle. Or so I thought.
-
How to create a full page cache within a CMS?
Not in golang. I use varnish as cache server before my application. See: https://github.com/mittwald/kube-httpcache
kubernetes-replicator
-
What if your Pods need to trust self-signed certificates?
I've built a small MutatingAdmissionWebhook controller [0] that handles this, via a pod annotation whose value is a secret with `ca.crt` inside, and it uses the (mostly) de facto standard openssl variables to configure the libraries, so that it works across pretty much everything I've tried it with off the shelf.
I build a bundle (though I may just move to trust-manager [1]) and replicate it into all namespaces with kubernetes-replicator [2], and then I can annotate any pod with
[0] https://github.com/microcumulus/ca-injector
[1] https://github.com/cert-manager/trust-manager
[2] https://github.com/mittwald/kubernetes-replicator
-
To anyone hosting in Kubernetes: Do you put all of your apps in one namespace (e.g., default), or one app per namespace?
Whichever way you go, I’ve successfully used this to replicate secrets: https://github.com/mittwald/kubernetes-replicator
- GitHub - mittwald/kubernetes-replicator: Kubernetes controller for synchronizing secrets & config maps across namespaces
What are some alternatives?
cache - Mango Cache 🥭 - Partial implementation of Guava Cache in Go (golang).
KubernetesCRDOperator - A sample about Kubernetes controller which can work with CRD to implement Operator pattern.
varnish-operator - Run and manage Varnish clusters on Kubernetes
aws-cloud-map-mcs-controller-for-k8s - K8s controller implementing Multi-Cluster Services API based on AWS Cloud Map.
varnish-towncrier - Distribute cache invalidation requests to a fleet of varnish instances.
secrets-manager - A daemon to sync Vault secrets to Kubernetes secrets
varnish-modules - Collection of Varnish Cache modules (vmods) by Varnish Software
kubed - 🛡️ Kubernetes Config Syncer (previously kubed) [Moved to: https://github.com/kubeops/config-syncer]
skipper - An HTTP router and reverse proxy for service composition, including use cases like Kubernetes Ingress
config-syncer - 🛡️ Kubernetes Config Syncer (previously kubed)
k8tz - Kubernetes admission controller and a CLI tool to inject timezones into Pods and CronJobs
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets