ingress | Kubernetes Ingress controller with integrated Wallarm | Runtime Evironment library

I am having a problem using Kubernetes Ingress with a ASP.NET core web API.

Lets say I have a web API with three controllers (simplified code to demonstrate three routes /, /ep1, /ep2):

I am learning kubernetes and got into a point where I am very confused. I have installed metallb and ingress-nginx so it is possible to access content from outside. I saw several examples that are using nginx image running in pod despite they are also using ingress-nginx.

Isn't ingress-nginx capable to do all work as nginx image? Otherwise what roles those two play?

I need to deploy express server where I would like to utilize some nginx features like gzip so it is where reverse proxy comes.

So do I need to make it work on ingress-nginx level or from nginx image? And if I need nginx image does it mean that I need to run separately nginx image and my built node image with my express app?

How to match a a word before a specific charachter using sed in bash?

In my scenario I would need to match the metrics names in the entire string which occurs only before {.

The below is the string I am working on.

I originally posted this question as an issue on the GitHub project for the AWS Load Balancer Controller here: https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/2069.

I'm seeing some odd behavior that I can't trace or explain when trying to get the loadBalacnerDnsName from an ALB created by the controller. I'm using v2.2.0 of the AWS Load Balancer Controller in a CDK project. The ingress that I deploy triggers the provisioning of an ALB, and that ALB can connect to my K8s workloads running in EKS.

Here's my problem: I'm trying to automate the creation of a Route53 A Record that points to the loadBalancerDnsName of the load balancer, but the loadBalancerDnsName that I get in my CDK script is not the same as the loadBalancerDnsName that shows up in the AWS console once my stack has finished deploying. The value in the console is correct and I can get a response from that URL. My CDK script outputs the value of the DnsName as a CfnOutput value, but that URL does not point to anything.

In CDK, I have tried to use KubernetesObjectValue to get the DNS name from the load balancer. This isn't working (see this related issue: https://github.com/aws/aws-cdk/issues/14933), so I'm trying to lookup the Load Balancer with CDK's .fromLookup and using a tag that I added through my ingress annotation:

In my GCP project, I have a python API running in a docker container (using connexion). I want to expose the API (with an API key) using API Gateway.

When I deploy the docker container with --ingress internal, I get Access is forbidden. on API calls over the Gateway. So the API gateway cannot access the Google Run container. When I use --ingress all, all works as expected, but then my internal API is accessible from the web, which is not what I want.

I created a service account for this:

I wish to create a helm chart to deploy an app that has multiple different pods (hence multiple deployment manifests). Here's the structure of the chart:

I'm trying to create an internal ingress for inter-cluster communication with gke. The service that I'm trying to expose is headless and points to a kafka-broker on the cluster.

However when I try to load up the ingress, it says it cannot find the service?

i'm working on a new idea for which I've created a setup as follows on Azure Kubernetes:

1. 1 cluster
2. 1 node pool in said cluster
3. 1 deployment which creates 2 pods in the pool
4. 1 load balancer service balancing requests between the 2 pods

I'm trying to submit a json request into the loadbalancer from outside the cluster with an AKS IP, to which i encounter 502 Bad Gateway issues.

This is my deployment file

We are currently confused/concerned by the development of storage cost for the underlying Storage Account of a Time Series Insights Instance.

Time Series Insights Ingress Received Bytes shows an amount of 1.5 GB for the last 30 days:

If I look at the related storage account for the same time span I see an ingress of 7.9 TB:

I know that TSI needs some space for additional indices and so on but this difference is very surprising and will result in a problem when we scale up our solution.

We set the Warm Storage Retention to the maximum of 31 Days.

Is this behavior something to expect when using Time Series Insights or is there anything we can do about this to reduce the usage of the Storage Account? I can not find anything about this behavior in the documentation.