Hi @ManuPhilip I executed the command kubectl get nodes -o yaml | grep pods and got the below output
for the command kubectl get pods --all-namespaces | grep Running | wc -l 
How do I increase the pod limit on nodes?
Hi @ManuPhilip I executed the command kubectl get nodes -o yaml | grep pods and got the below output
for the command kubectl get pods --all-namespaces | grep Running | wc -l
How do I increase the pod limit on nodes?
Hi @ManuPhilip yes we have tainted a node to run specific workloads. But here the context is not about taints and tolerations. we are not able to deploy pods on the other 3 nodes. Please refer to the snapshot it says too many pods. Not sure why it is showing the above message.
@srbose-msft @ManuPhilip requesting your assistance in resolving this issue.
Hi @srbose-msft thanks for the reply. Here I am interested in the uniform distribution of pods across the 3 nodes.
Hi @srbose-msft looking forward for your reply please help to resolve the issue as it is affecting the node performance.
Hi @tbgangav-MSFT we are facing the below error when executing the code
Failed
Cannot validate argument on parameter 'Subscription'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. (The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.)
System.Management.Automation.ParameterBindingValidationException: Cannot validate argument on parameter 'Subscription'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. ---> System.Management.Automation.ValidationMetadataException: The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
can you plese help me to resolve the issue?
@srbose-msft we are already using nginx controller in our development setup and are able to achieve gzip compression. And for production setup we switched to azure application gateway since we wanted WAF ( web application firewall) which was missing in nginx ingress controller. But just learned that azure application gateway doesn't support compression. And in the documentation
gateway
it is mentioned gzip compression as one of the feature. Already someone has raised a issue regarding gzip compression in app gateway
23204
can you please update me whether they have worked on this issue and is available in the newer versions?
Hi @srbose-msft yes we are using application gateway with AKS cluster. we have created this app gateway through azure portal . And in our AKS cluster we deployed ingress controller via helm using this link https://azure.github.io/application-gateway-kubernetes-ingress/setup/install-existing/
@srbose-msft we are using the below annotation in our ingress rules file. so as of now we are not using the annotation appgw.ingress.kubernetes.io/rewrite-rule-set .
annotations:
kubernetes.io/ingress.class: azure/application-gateway
appgw.ingress.kubernetes.io/health-probe-path: "/api/v1/healthCheck"
appgw.ingress.kubernetes.io/ssl-redirect: "true"
appgw.ingress.kubernetes.io/health-probe-port: "XXXX"
appgw.ingress.kubernetes.io/health-probe-timeout: "30"
Is this newly added annotation ?
couldn't find this annotation in this list https://azure.github.io/application-gateway-kubernetes-ingress/annotations/
hi @ManuPhilip I am using this version mcr.microsoft.com/azure-application-gateway/kubernetes-ingress:1.4.0-rc1. what is the fix can you please specify in detail?
Hi @tbgangav-MSFT we have multiple AKS cluster in different subscriptions so will the above code work if we have multiple susbscriptions or some changes need to be done to the code?
Hi @tbgangav-MSFT thanks for the reply. It would be quite helpful if you can specify or provide the exact changes to be done in the existing code so that code can be directly executed in the runbook. And also others can use the same code without modification.
Hi @ManuPhilip we resolved the issue by creating new nodepool and setting the max pods per node as 110. And we migrated our pods to this new node pool. And we are able to deploy our deployments. Thanks a lot for your assistance.