balancer | Load balancer that was presented at HighLoad | Load Balancing library

I am trying to deploy 2 containers on 2 different tasks (1 container per task), one is my frontend and the other is my backend server. I am trying to figure out how to configure the communication between them.

I saw that a load balancer in a service is a good option. However, should I configure load balancer for my front end server and another one for my backend? Meaning each time I have public-facing services and private services I need 2 load balancers?

I would like to only expose my front-end to the public internet and my backend will remain private (although I make API requests to the outside world - probably need to configure outbound route too?).

I would highly appreciate any information.

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:

I am running a GitHub agent inside AKS cluster with Docker installed. I can run it successfully with VFS storage driver, however I want to use Overlay 2 because it's faster. I get the following message:

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

Context: I followed this link on setting up AWS MSK and testing a producer and consumer and it is setup and working correctly. I am able to send and receive messages via 2 separate EC2 instances that both use the same Kafka cluster (My MSK cluster). Now, I would like to establish a data pipeline all the way from Eventhubs to AWS Firehose which follows the form:

Azure Eventhub -> Eventhub-to-Kafka Camel Connector -> AWS MSK -> Kafka-to-Kinesis-Firehose Camel Connector -> AWS Kinesis Firehose

I was able to successfully do this without the use of MSK (via regular old Kafka) but for unstated reasons need to use MSK now and I can't get it working.

Problem: When trying to start the connectors between AWS MSK and the two Camel connectors I am using, I get the following error:

These are the two connectors in question:

1. AWS Kinesis Firehose to Kafka Connector (Kafka -> Consumer)
2. Azure Eventhubs to Kafka Connector (Producer -> Kafka)

Goal: Get these connectors to work with the MSK, like they did without it, when they were working directly with Kafka.

Here is the issue for Firehose:

I have a bash script that checks if the CHECKURL variable has a response or not. If the url is not valid or doesn't exist the script immediately exits and echo a message "NOT VALID URL"

I have one problem in which the url https://valid-url-sample.com is a valid url however my IP is rejected on the load balancer because it only respond on 443 request from specific IP's. The result is the script stays running until I it requires me to control+c. I would like the script to handle this kind of condition and echoes "VALID BUT NOT REACHABLE", I also added timeout on the wget command but still no luck. any thoughts on how to handle this?

SCRIPT

I need some suggestions for best practicality, security and maintainability

The scenario is:

• We have a private VPC with some servers,
• We have users that can access server A and A only
• Some users can access A, and B.
• Other only B and so on.

They need to access to theses servers from home and office.

The current idea is having a multiuser OpenVPN server with IPTables blocking access to the servers that the user can't access

Is there another option using AWS tools (VPCs,Security Groups, ACLs, Load Balancers, or others)?

Or other solutions better than this one?

Draw of current arch:

• One boundary server that does the bridge from the open world to the Private VPC (With OpenVpn and IPTables)
• 5 servers inside the private VPC
• 10 Users with different levels of access

Thanks

The knative docs describe the following:

To configure DNS for Knative, take the External IP or CNAME from setting up networking, and configure it with your DNS provider as follows

• If the networking layer produced an External IP address, then configure a wildcard A record for the domain:

  # Here knative.example.com is the domain suffix for your cluster

  *.knative.example.com == A 35.233.41.212

• If the networking layer produced a CNAME, then configure a CNAME record for the domain:

  # Here knative.example.com is the domain suffix for your cluster

  *.knative.example.com == CNAME a317a278525d111e89f272a164fd35fb-1510370581.eu-central-1.elb.amazonaws.com

However, my environment doesn't have an external load balancer and hence no EXTERNAL-IP: