kubernetes-app | A set of dashboards and panels for kubernetes | Monitoring library

I have a simple Flink streaming app. It runs well in a cluster created by start-cluster.sh command.

Now based on the Flink tutorial, I hope to deploy it in application mode natively in a Kubernetes cluster created by k3d on macOS.

First, I created a cluster by k3d cluster create dev.

Here is my Dockerfile:

I found two interpretations to a formula used for over-provisioning resources in GKE when autoscaling.

According to the following two sources:

• Autoscaler and over-provisioning

• Autoscaling with GKE: Clusters and nodes

the formula:

When creating a Kubernetes service, I'm trying to understand what fields in the YAML service definition need to match to a PODs definition.

For example, given the service:

I've a strange behaviour when trying to do some load testing.

Environment :

• NGINX Ingress controller version: 0.44.0
• Kubernetes version : 1.17.8
• openidc.lua version : 1.7.4

Here's the situation :

• The nginx ingress controller is deployed as daemonset, and due to the openidc module, I activated the sessionAffinity to ClientIP.
• I have a simple stateless rest service deployed with a basic ingress which is tested for load (no sessionAffinity on that one).

When launching load testing on the rest service without the sessionAffinity ClientIP, I reach far beyond 25 req/s (about 130 req/s before the service resources begin to crash, that's another thing). But with the sessionAffinity activated, I only reach 25 req/s.

After some research, I found some interesting things, desribed like here : https://medium.com/titansoft-engineering/rate-limiting-for-your-kubernetes-applications-with-nginx-ingress-2e32721f7f57

So the formula, as the load test should always be served by the same nginx pod, should be : successful requests = period * rate + burst

So I did try to add the annotation nginx.ingress.kubernetes.io/limit-rps: "100" on my ingress, but no luck, still the same 25 req/s.

I also tried different combinations of the following annotations : https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#rate-limiting, but no luck either.

Am I missing something ?

i am not able to understand one point in the rate-limiting of Nginx ingress

i was referring to one article regarding rate limiting with nginx ingress : https://medium.com/titansoft-engineering/rate-limiting-for-your-kubernetes-applications-with-nginx-ingress-2e32721f7f57#:~:text=When%20we%20use%20NGINX%20ingress,configure%20rate%20limits%20with%20annotations.&text=As%20an%20example%20above%2C%20the,qps)%20on%20the%20Hello%20service.

in limitation section at last

It applies to the whole ingress and is not able to configure exceptions, eg. when you want to exclude a health check path /healthz from your service.

if i am creating two ingresses with different names, one has path /hello1 and another /hello2 both pointing to the same service backend.

Now if i am adding rate limiting to only one ingress or path /hello1 will it affect another? if the same host or domain is there ???

ingress 1 : example.com/hello1 - rate-limit set

ingress 2 : example.com/hello2 no rate limiting

Thanks in advance

I have an infrastructure where AWS login happens on a Role basis requires MFA from MS authenticator which pops up on Mobile device for Accept or Decline. Normally on CLI, we use saml2aws and it generates temporary access key secret key with assume role.

I am trying to use aws-sdk in my nodejs and trying to validate the credentials but not getting any popup and gets below error.

Please suggest the method or way to achieve this.

There is a kubernetes baremetal cluster which has 7 nodes. Installed is helm and added a helm repo added

• ingress-nginx https://kubernetes.github.io/ingress-nginx In my lan i created a dns A record which is resolvable in my lan.

What works: https://matthewpalmer.net/kubernetes-app-developer/articles/kubernetes-ingress-guide-nginx-example.html

I am able to access the apple and the banana location on the dns A record mentioned before.

When i deploy a default nginx image with a service with port 80 and of type cluster-ip the following nginx-ingress resource does not work

kubectl run nginx --image=nginx ; kubectl exposed pod nginx --port=80

I want to install Kubernetes on 3 Masters, 3 ETCDs and 2 Nodes by Kubespray. but kubespray playbook stops in the middle of the process. At one point, it print this message, but the process continued: