ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #kubernetes
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?
I'm trying to use NodePort with kind but somehow it doesn't want to work. I've successfully deployed the following cluster: apiVersion: kind.x-k8s.io/v1alpha4 kind: Cluster nodes: - role: control-plane extraPortMappings: - containerPort: 80 hostPort: 30000 listenAddress: "0.0.0.0" # Optional, defaults to "0.0.0.0" protocol: tcp # Optional, defaults to tcp -
I am using a Windows 10 Pro machine. When I run netstat , it is showing kubernetes:port as foreign address in active connections. What does this mean? I have checked and there is no kubernetes cluster running on my machine. How do I close these connections? Minikube status: $ minikube status host: kubelet: apiserver: kubectl:
I need some advise on an issue I am facing with k8s 1.14 and running gitlab pipelines on it. Many jobs are throwing up exit code 137 errors and I found that it means that the container is being terminated abruptly. Cluster information: Kubernetes version: 1.14 Cloud being used: AWS EKS Node: C5.4xLarge After digging in, I found the below logs: **kubelet: I01
I created the eks cluster trying to connect it with local cli, for that, I installed the aws-cli and also provide the right 'aws configure' credentials. The user which I am using to connect with the aws have the EKS related policy. Still I am getting the following Error ... E0209 21:09:44.893284 2465691 memcache.go:238] couldn't get current server API group
answered · 25 Feb 2022, 07:39 UTC
answered · 01 Nov 2021, 03:46 UTC
docker