The following pod definition successfully executes a readinessProbe, which makes a request to the service service-am-i-ready that connects to pods on the same cluster. apiVersion: v1 kind: Pod metadata: creationTimestamp: null labels: run: ready-if-service-ready name: ready-if-service-ready spec: containers: - image:…
I'm following along with a video explaining blue/green Deployments in Kubernetes. They have a simple example with a Deployment named blue-nginx and another named green-nginx. The blue Deployment is exposed via a Service named bgnginx. To transfer traffic from the…
Hi I've deployed single MySQL db instance in Azure via the YAML file in Azure Kubernetes service. I can get into the container via CLI when I'm inside my cluster. I would like to connect with db instance via external…
Following the example on kubernetes.io I'm trying to connect to an external IP from within the cluster (and i need some port proxy, so not ExternalName service). However it is not working. This is the response I'm expecting ubuntu:/opt$ curl…
I am running my minikube as docker image. I am trying to expose my service to outside world using Nodeport. This is my yaml file. apiVersion: apps/v1 kind: Deployment metadata: name: docker-hello-world labels: app: docker-hello-world spec: selector: matchLabels: app: docker-hello-world…
I am new to K8s, and I am facing issues trying to connect to K8s NodePort service from outside the cluster. I am unable to load the nginx default page when I try accessing it from my local machine using…
I have the following pod definition to run a basic instance of nginx --- apiVersion: v1 kind: Pod metadata: name: basic labels: appName: static-website spec: containers: - image: nginx name: basic I have made the following service definition apiVersion: v1…
In my Kubernetes cluster, I have a single pod (i.e. one replica) with two containers: server and cache. I also have a Kubernetes Service that matches my pod. If cache is crashing, when I try to send an HTTP request…
I can't access a service from a pod, when I run the curl serviceIP:port command from my pod console, I get the following error: root@strongswan-deployment-7bc4c96494-qmb46:/# curl -v 10.111.107.133:80 * Trying 10.111.107.133:80... * TCP_NODELAY set * connect to 10.111.107.133 port 80…
I have created a docker image ( java web application ), created a kubernetes cluster with 1 master and 1 worker, created a deployment and a service. All the resources seem to run fine as I have checked by 'kubectl…