load-balancer | Load balancing reference code | Load Balancing library

A CrashloopBackOff means that you have a pod starting, crashing, starting again, and then crashing again.

Maybe the error come from the application itself that it can not connect to database, redis,...

You may find something useful here:

My kubernetes pods keep crashing with "CrashLoopBackOff" but I can't find any log

the issue is with the airflow Docker image you are using.

The ENTRYPOINT I see is a custom .sh file you have written and that decides whether to run a webserver or scheduler.

Airflow scheduler submits a pod for the tasks with args as follows

For an update with zero downtime you should consider using more than one pod.
You can also tweak your maxSurge and maxUnavailable values (1).
One-second timeout seems a bit low, consider raising those values.
Finally, you can find an extensive guide on rolling updates in the google docs.

have you seen this article from official side? Pay attention on Log files overview section.

When deploying Fluent Bit to Kubernetes, there are three log files that you need to pay attention to. C:\k\kubelet.err.log

Also you can find Fluent GitHub Community and create an issue there to have better support from its contributors

There is a Slack channel for Fluent

From this what you have the Ingress already should work and your services are meant to be private(if you set like this in your public cloud cluster), except the Ingress itself. You can update the ConfigMap to use the PROXY protocol so that you can pass proxy information to the Ingress Controller:

I believe you are using a static IP address with the NGINX Ingress controller service. This issue pops up if the cloud controller manager cannot find the static Azure Public Ip Address resource in the containing resource group mentioned in the NGINX Ingress Controller's service annotation (if no resource group is explicitly specified with a service annotation, it will look for the Azure Public IP Address resource in the AKS cluster's node resource group)

If you have created the static Azure Public IP Address resource in the node resource group then please ensure that the Azure Public IP address resource exists.

If you have created the static Azure Public IP Address resource in a different resource group, then:

• Please ensure the cluster identity used by the AKS cluster has delegated permissions to the other resource group, such as Network Contributor.

https://aws.amazon.com/blogs/networking-and-content-delivery/accessing-an-aws-api-gateway-via-static-ip-addresses-provided-by-aws-global-accelerator/

This blog shows how to configure the architecture given in the question using AWS console (just disable the global accelerator option). The key takeaway is that the application load balancer uses target type IP and resolves the VPC endpoint domain name manually in step 2. The other two options, instance (target is an EC2 instances) and lambda (target is an AWS Lambda function) cannot be used.

The ec2.InterfaceVpcEndpoint construct has no output which directly gives an IP address. The underlying CloudFormation resource also does not support it. Instead, you will have to use the vpcEndpointDnsEntries property of ec2.InterfaceVpcEndpoint and resolve the domain names to IP addresses in your code (the console configuration also required the same domain name resolution). You can use an IpTarget object in your ApplicationTargetGroup.

At this point, you will run into one final roadblock due to how CDK works under the hood. If you have all your resources defined in one CDK application, the value for each parameter (or a reference to the value using an underlying CloudFormation functions like Ref, GetAtt, etc.) needs to be available before the synthesize step, since that's when all templates are generated. AWS CDK uses tokens for this purpose, which during synthesis resolve to values such as {'Fn::GetAtt': ['EndpointResourceLogicalName', 'DnsEntries']. However since we need the actual value of the DNS entry to be able to resolve it, the token value won't be useful.

One way to fix this issue is to have two completely independent CDK applications structured this way:

• Application A with VPC and interface endpoint. Define the vpcEndpointDnsEntries and VPC-ID as outputs using CfnOutput.
• Application B with the rest of the resources. You will have to write code to read outputs of the CloudFormation stack created by Application A. You can use Fn.importValue for VPC ID, but you cannot use it for the DnsEntries output since it would again just resolve to a Fn::ImportValue based token. You need to read the actual value of the stack output, using the AWS SDK or some other option. Once you have the domain name, you can resolve it in your typescript code (I am not very familiar with typescript, this might require a third party library).

Image credits:

• https://docs.aws.amazon.com/cdk/v2/guide/apps.html

You need to manually create eips either through cli or console and add there allocation id as comma separated in the annotation, it'll get created. Make sure to have same number of subnets and eips as your availability zones.

It is a missing feature.

Other tools like Pulumi (based on Terraform) have been able to do it via the ARN of the CLB.

Terraform itself can do it via the name of the CLB.

The docs should be similar across the board but just to double-check this, the CDK API docs for ELB v2 show that you can lookup application load balancers (ALBs) and network load balancers (NLBs) as you've mentioned.

Similarly (to cross out possible language-specific CDK implementations), I looked through the entire CDK API docs for ELB v1 which refers to classic load balancers (CLBs). There are no lookup methods.

Considering Terraform has done this, it means that there must be an AWS API for it - perhaps try seeing if you can use AwsSdkCall to make a custom call and obtain the data needed.