ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #kubernetes
Jaeger's all-in-one image and Operator-based deployments expose the Query UI on port 16686 and collector ingestion on ports 14268 , 14250 , and 4317/4318 (OTLP). As of Jaeger 1.x, these endpoints ship without integrated authentication or authorization, so anyone who can reach them can read traces — which often contain sensitive span tags such as URLs, user i
We have an AKS cluster and sometimes we end up with an issue where a deployment needs a restart (e.g. cached data has been updated and we want to refresh it or there is corrupt cache data we want to refresh). I've been using the approach of scaling the deployment to 0 and then scaling it back up using the commands below: kubectl scale deployments/<deploym
I understand that services use a selector to identify which pods to route traffic to by thier labels. apiVersion: v1 kind: Service metadata: name: svc spec: ports: - name: tcp protocol: TCP port: 443 targetPort: 443 selector: app: nginx Thats all well and good. Now what is the difference between this selector and the one of the spec.selector from the deploym
Infrastructure Management Trade-offs When integrating Kubernetes clusters into Rancher, the choice between Provisioned and Imported clusters determines where the source of truth for infrastructure resides. Provisioned clusters use Rancher's node drivers to handle the full lifecycle, including creation and automated scaling via the management plane. Imported
Akka Cluster documents rolling upgrades in which nodes of adjacent versions coexist while akka.cluster.allow-weakly-upgraded-nodes is enabled. That tolerance assumes message and event serialization remains backward compatible, typically through a schema-evolution format rather than Java serialization. The alternative is orchestration-driven replacement, such
Whenever I am trying to run the docker images, it is exiting in immediately. CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ae327a2bdba3 k8s-for-beginners:v0.0.1 "/k8s-for-beginners" 11 seconds ago Exited (1) 10 seconds ago focused_booth As per Container Logs standard_init_linux.go:228: exec user process caused: no such file or directory I have create
I'm trying to deploy a single web application to Minikube on my Mac, and then access it in the browser. I'm trying to use the simplest of setups, but it's not working, I just get a "connection refused" error and I can't figure out why. This is what I'm trying: $ minikube start --insecure-registry=docker.example.com:5000 😄 minikube v1.12.3 on Darwin 10.14.6 ✨
This page describes how to observe the status and health of resources that are dynamically allocated with DRA. Observability of dynamic resources You can check the status of dynamically allocated resources by using any of the following methods: kubelet device metrics ResourceClaim status Device heal
Integration Boundary The Argo CD ApplicationSet controller pairs with the Git generator to create Application resources from JSON or YAML files stored in a repository path. A single templated ApplicationSet can fan out applications across many target clusters, and the controller reconciles child Applications as the generator source changes. Deletion Behavior
jaegertracing
rancher
docker
argocd