cni | Istio CNI to setup kubernetes pod namespaces | Service Mesh library

I have a cluster in AWS created by these instructions.

Then I tried to add nodes in this cluster according to this documentation.

It seems that the nodes fail to be created with vpc-cni and coredns health issue type: insufficientNumberOfReplicas The add-on is unhealthy because it doesn't have the desired number of replicas.

The status of the pods kubectl get pods -n kube-system:

I am running a 3 Node Kubernetes cluster with Flannel as CNI. I used kubeadm to setup the cluster and the version is 1.23.

My pods need to talk to external hosts using DNS addresses but there is no DNS server for those hosts. For that, I have added their entries in /etc/hosts on each node in cluster. The nodes can resolve the host from DNS but Pods are not able to resolve them.

I tried to search this problem over internet and there are suggestions to use HostAlias or update /etc/hosts file inside container. My problem is that the list of hosts is large and it's not feasible to maintain the list in the yaml file.

I also looked if Kubernetes has some inbuilt flag to make Pod look for entries in Node's /etc/hosts but couldn't find it.

So My question is -

1. Why the pods running on the node cannot resolve hosts present in /etc/hosts file.
2. Is there a way to setup a local DNS server and asks all the Pods to query this DNS server for specific hosts resolutions?

Any other suggestions or workarounds are also welcomed.

I am trying to understand the usage of the ip addresses from my vpc in the eks with fargate environment. I can see that each pod has its own private ip address, which seems to be the same ip address for fargate node as well. It seems that the ENI allocates a single primary address for a EC2 node and many ip address as secondary based on the size, but I cannot find the same information on fargate. Does that mean it does not have any secondary ip addresses allocated ?

Extending on the question, it seems that a network load balancer requires a minimum of 8 free ip addressses to be created, Does that mean it blocks all the 8 ?

I am a bit desperate and I hope someone can help me. A few months ago I installed the eclipse cloud2edge package on a kubernetes cluster by following the installation instructions, creating a persistentVolume and running the helm install command with these options.

I'm trying to set up FluentBit for my EKS cluster in Terraform, via this module, and I have couple of questions:

cluster_identity_oidc_issuer - what is this? Frankly, I was just told to set this up, so I have very little knowledge about FluentBit, but I assume this "issuer" provides an identity with needed permissions. For example, Okta? We use Okta, so what would I use as a value in here?

cluster_identity_oidc_issuer_arn - no idea what this value is supposed to be.

worker_iam_role_name - as in the role with autoscaling capabilities (oidc)?

This is what eks.tf looks like:

I have 2 kubernetes clusters in the IBM cloud, one has 2 Nodes, the other one 4.

The one that has 4 Nodes is working properly but at the other one I had to temporarily remove the worker nodes due to monetary reasons (shouldn't be payed while being idle).

When I reactivated the two nodes, everything seemed to start up fine and as long as I don't try to interact with Pods it still looks fine on the surface, no messages about inavailability or critical health status. OK, I deleted two obsolete Namespaces which got stuck in the Terminating state, but I could resolve that issue by restarting a cluster node (don't exactly know anymore which one it was).

When everything looked ok, I tried to access the kubernetes dashboard (everything done before was on IBM management level or in the command line) but surprisingly I found it unreachable with an error page in the browser stating:

503: Service Unavailable

There was a small JSON message at the bottom of that page, which said:

This is sort of strange behavior in our K8 cluster.

When we try to deploy a new version of our applications we get:

Following the documentation I try to setup the Seldon-Core quick-start https://docs.seldon.io/projects/seldon-core/en/v1.11.1/workflow/github-readme.html

I don't have LoadBalancer so I would like to use port-fowarding for accessing to the service.

I run the following script for setup the system:

I have a Docker Swarm running a container with our custom code (.net core 3.1 on Linux) in with no issue. I have just setup a test 4 node Kubernetes cluster using Microk8s. When I load the image to Kubernetes, it appears to go through fine but the container starts and then stops immediately with error "Back-off restarting failed container". Looking at the error from the pod, I get "It was not possible to find any installed .NET Core SDKs. Did you mean to run .NET Core SDK commands? Install a .NET Core SDK from: https://aka.ms/dotnet-download".

The image is the same image running in the Swarm. My searches have led me to ENTRYPOINT potentially being the issue from the build dockerfile but I haven't had any luck with with changes to this. I have put my dockerfile below in case it is relevant to this problem.