How to deploy a self-managed Kubernetes cluster using Azure VMs with Kubeadm?

Question

How to deploy a self-managed Kubernetes cluster using Azure VMs with Kubeadm?

Ali Raza 0

Hello, I am trying to deploy a self-managed Kubernetes cluster in Azure VMs using Kubeadm with one master and one worker node. However, when I create an nginx ingress, its load balancer service doesn't get a public IP and remains in a pending state, even though both VMs are behind the same load balancer. Is there any way to resolve this issue without using AKS, and deploying the cluster only with VMs?

Anveshreddy Nimmala 3,550 Reputation points Microsoft External Staff Moderator

2024-01-30T04:28:49.6666667+00:00

Hello Ali Raza, Welcome to microsoft Q&A,Thankyou for posting your query here. could you please confirm that you have created an Azure Load Balancer and that both your master and worker nodes are behind it? could you please provide the YAML file you used to create the nginx ingress? This will help me understand how you have configured the service. if have you tried creating a Kubernetes Service of type LoadBalancer to expose your nginx ingress? This should automatically create an Azure Load Balancer with a public IP address. could please check and provide below information to debug in detail.

Ali Raza 0

Yes, My both VMs are behind same load balancer. I installed Nginx-Ingress with helm.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: admin-ingress
  namespace: admin-lite
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt
    nginx.ingress.kubernetes.io/rewrite-target: /$1
    nginx.ingress.kubernetes.io/use-regex: "true"
spec:
  ingressClassName: nginx
  tls:
  - hosts:
    - tracks.mysite.live
    secretName: tls-secret
  rules:
  - host: tracks.mysite.live
    http:
      paths:
 
      - path: /(.*)
        pathType: Prefix
        backend:
          service:
            name: admin-ui
            port:
              number: 3001

1 answer

Your answer

Anveshreddy Nimmala 3,550 Reputation points Microsoft External Staff Moderator

2024-01-30T04:28:49.6666667+00:00

Hello Ali Raza, Welcome to microsoft Q&A,Thankyou for posting your query here. could you please confirm that you have created an Azure Load Balancer and that both your master and worker nodes are behind it? could you please provide the YAML file you used to create the nginx ingress? This will help me understand how you have configured the service. if have you tried creating a Kubernetes Service of type LoadBalancer to expose your nginx ingress? This should automatically create an Azure Load Balancer with a public IP address. could please check and provide below information to debug in detail.
Ali Raza 0 Reputation points

2024-01-31T08:59:40.24+00:00

Yes, My both VMs are behind same load balancer. I installed Nginx-Ingress with helm.

apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: admin-ingress namespace: admin-lite annotations: cert-manager.io/cluster-issuer: letsencrypt nginx.ingress.kubernetes.io/rewrite-target: /$1 nginx.ingress.kubernetes.io/use-regex: "true" spec: ingressClassName: nginx tls: - hosts: - tracks.mysite.live secretName: tls-secret rules: - host: tracks.mysite.live http: paths: - path: /(.*) pathType: Prefix backend: service: name: admin-ui port: number: 3001

Answer 1

Hello Ali Raza, Thankyou for providing configuration details, Based on the provided YAML manifest, it seems that you have created an Ingress resource for the admin-lite namespace with a host of tracks.mysite.live. The Ingress resource is configured to use the nginx ingress class and has a TLS secret named tls-secret. The Ingress resource also has a rewrite target annotation that rewrites the URL path to / and a path type of Prefix. The backend service for the Ingress resource is named admin-ui and listens on port 3001. However, it's not clear from the provided YAML manifest whether you have created a Service resource for the admin-ui backend service. you need to create a Service resource that exposes the admin-ui backend service. You can create a Service resource by running the following command: kubectl create service clusterip admin-ui --tcp=3001:3001 -n admin-lite This command creates a Service resource named admin-ui in the admin-lite namespace that exposes the admin-ui backend service on port 3001. The Service resource is of type ClusterIP, which means that it's only accessible from within the cluster. Once you have created the Service resource, you should be able to access the admin-ui backend service through the Ingress resource at the tracks.mysite.live host. if the load balancer service for the Ingress resource is still in a pending state, it's possible that there is an issue with the load balancer configuration. You may need to check the logs for the load balancer to see if there are any errors. Hope this helps you, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered.

Anveshreddy Nimmala 3,550 Reputation points Microsoft External Staff Moderator

2024-02-02T03:39:25.9233333+00:00

Hello Ali Raza, If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!.
Anveshreddy Nimmala 3,550 Reputation points Microsoft External Staff Moderator

2024-02-05T03:33:39.82+00:00

Hello Ali Raza, If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!.

Share via

How to deploy a self-managed Kubernetes cluster using Azure VMs with Kubeadm?

1 answer

Your answer