Check the cluster access.
2.Check helm installed or not? helm version
3.Create a k8 namespace for ingres
Currently we have
az group create --name myResourceGroup --location eastus
az aks create --resource-group myResourceGroup --name myAKSCluster --enable-managed-identity --node-count 2 --generate-ssh-keys
az aks get-credentials --resource-group myResourceGroup --name myAKSCluster
**Ingress reference:
https://learn.microsoft.com/en-us/azure/aks/ingress-basic?tabs=azure-cli
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update
helm install ingress-nginx ingress-nginx/ingress-nginx \
--create-namespace \
--namespace ingress-basic \
--set controller.service.annotations."service\.beta\.kubernetes\.io/azure-load-balancer-health-probe-request-path"=/healthz \
--set controller.service.externalTrafficPolicy=Local
kubectl get svc -n ingress-basic
#################################################
raj [ ~ ]$ kubectl get svc -n ingress-basic
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
ingress-nginx-controller LoadBalancer 10.0.195.209 4.255.42.121 80:32709/TCP,443:31306/TCP 10m
#################################################
**Update Ingress Flask code:
https://github.com/shivscloud/azure-k8-manifest/blob/main/AKS-Flask-Ingress
kubectl apply -f Aks-Ingresss.yml
http://4.255.42.121
********Using Application gateway ingress controller
https://learn.microsoft.com/en-us/azure/application-gateway/ingress-controller-overview
0 Comments