ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #kubernetes
I am creating an InfluxDB deployment in a Kubernetes cluster (v1.15.2), this is my yaml file: apiVersion: extensions/v1beta1 kind: Deployment metadata: name: monitoring-influxdb namespace: kube-system spec: replicas: 1 template: metadata: labels: task: monitoring k8s-app: influxdb spec: containers: - name: influxdb image: registry.cn-hangzhou.aliyuncs.com/go
Asked · 02 Jun 2022, 18:33 UTC
answered · 07 Jun 2022, 13:45 UTC
I had seen official documentation: https://kubernetes.io/docs/tasks/setup-konnectivity/setup-konnectivity/ but I still failed to understand its meaning. I have few questions: If the connectivity service provides TCP level proxy, so what does the proxy include? If I used the service on a cluster, what will happen to My pods, services, quality for communicatio
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
I am currently using the following to attempt to spread Kubernetes pods in a given deployment across all Kubernetes nodes evenly: spec: affinity: podAntiAffinity: preferredDuringSchedulingIgnoredDuringExecution: - weight: 100 podAffinityTerm: topologyKey: kubernetes.io/hostname labelSelector: matchExpressions: - key: app operator: In values: - api However, 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
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 ✨
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
docker