Explore >> Select a destination
|
You are here 
|
blogops.mixinet.net | ||
| | | | |
foo.zone
|
|
| | | | | [AI summary] The text describes a comprehensive setup of a Kubernetes cluster (k3s) with various services and tools. It includes a private Docker registry, multiple applications like Anki Sync Server, Miniflux, and others, all utilizing NFS storage and UID/GID mapping for compatibility. The setup also involves relayd for traffic routing, Ingress controllers, and custom Helm charts for deployment. The author plans to expand on monitoring and observability in future posts. | |
| | | | |
platformengineering.org
|
|
| | | | | Learn what KRO (Kubernetes Resource Orchestrator) is and how it simplifies Kubernetes app deployment by creating custom APIs that group resources, reducing YAML complexity and making management easier for developers. | |
| | | | |
www.architect.io
|
|
| | | | | Learn to build a Go service and deploy it to a Kubernetes cluster in AWS | |
| | | | |
hjr265.me
|
|
| | | Toph needs a few MongoDB features that only work in replica set mode. Take Change Streams, for example. It is unavailable in standalone mode. To ease development, all of Toph's application codebases come with Docker Compose files. With just a single docker-compose up, I can have any of Toph's applications running in a development environment. But having MongoDB start in replica set mode has been a bit of work. You see, simply starting three nodes and then going in to configure them to be in a replica set wasn't something I wanted to do. | ||
