I am using the YAML file to deploy the container on Kubernetes with some replication factor on a hosted machine.

YAML File

apiVersion: apps/v1
kind: Deployment
metadata:
  name: mojo-deployment
  labels:
    app: mojo
spec:
  selector:
    matchLabels:
      app: mojo
  replicas: 3
  template:
    metadata:
      labels:
        app: mojo
    spec:
      containers:
        - name: mojo
          image: mojo:1.0.1
          ports:
            - containerPort: 9000

---
#Services Info
apiVersion: v1
kind: Service
metadata:
  name: mojo-services
spec:
  selector:
    app: mojo
  ports:
    - protocol: TCP
      port: 80
      targetPort: 9376

---

#Ingress Configuration
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: mojo-ingress
  annotations:
    kubernetes.io/ingress.class: mojo
spec:
  backend:
    serviceName: mojo-services
    servicePort: 80

Steps:

1. Build Docker image using `docker build -t mojo:1.0 .
2. docker image ls show me an image id.
3. Skipping docker build command to deploy image on container. Do I need to do it? or kubectl service will take care of it.
4. Run kubectl apply -f Prod.yaml. It shows

deployment.apps/mojo-deployment created

service/mojo-services created

ingress.networking.k8s.io/mojo-ingress created

5. kubectl get service returns

   

6. kubectl get pod returns

7. kubectl get deployment returns

Questions?

1. Do I need to build the container before deploying YAML file? I tried it but still kubernetes not running.

2. Why all pods are showing Pending status.

3. Deployment is also showing pending status.

4. Though I am trying to access the Ingress with :80 and cannot access it.

Edit

pod description

Name:           mojo-deployment-6665bdc557-s57m7
Namespace:      default
Priority:       0
Node:           <none>
Labels:         app=mojo
            pod-template-hash=6665bdc557
Annotations:    <none>
Status:         Pending
IP:            
IPs:            <none>
Controlled By:  ReplicaSet/mojo-deployment-6665bdc557
Containers:
mojo:
 Image:        mojo:1.0
 Port:         9000/TCP
 Host Port:    0/TCP
 Environment:  <none>
 Mounts:
 /var/run/secrets/kubernetes.io/serviceaccount from default-token-tjx6p 
(ro)
Conditions:
Type           Status
PodScheduled   False
Volumes:
default-token-tjx6p:
 Type:        Secret (a volume populated by a Secret)
 SecretName:  default-token-tjx6p
 Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
            node.kubernetes.io/unreachable:NoExecute for 300s
 Events:
  Type     Reason            Age                 From               

Message ---- ------ ---- ---- ------- Warning FailedScheduling 70s (x45 over 67m) default-scheduler 0/1 nodes are available: 1 node(s) were unschedulable.

Edit 2

After removing the taint from the master node. 1. kubectl get node returns

2. kubectl get pod returns

3. kubectl describe node : https://gist.github.com/amixpal/333bffd6ab91def749267f30d4ffb079