ws-tool | Develop Tool to Test WebSocket | Websocket library

So I changed my approach a bit.

WASM (to my understanding) is meant to be a cross-platform platform solution. Instead of publishing to Beanstalk, I just published it manually for my desired OS (which was Linux x64) and spun up an EC2 instance.

I installed NGINX, created my domain routing in Route 53 and then proceeded to FTP the published files into the directory I prepared on the AWS instance.

This worked like a charm. You do lose some of the Beanstalk default perks such as ELB but you can always just set that up manually if your application needs it.

I was able to solve this issue by fixing the errors when mvn install -e is used.

• First of all I upgraded the jaxb-impl and jaxb-xjc versions from 2.1.6 to 2.2.10.

• I added below jaxb-core and jaxws-tools dependencies.

Here is the updated part of my pom.xml:

Replace:

Turned out the jaxws-tools required several jakarta libraries in version 3.0.0. I added them to configuration and wsimport now works

I recommend you to install and use pyenv, a Python Version Management. Once intalled pyenv, install python 3.7:

I found a solution to my answer. The change I made was to remove the tag from the for the toolbar.

Here is the fixed plugin.xml section:

There are a lot of materials about Kubernetes on official site and I encourage you to check it out:

• Kubernetes.io

I divided this answer on parts:

• CNI
• Troubleshooting

What is CNI?

CNI (Container Network Interface), a Cloud Native Computing Foundation project, consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support and the specification is simple to implement.

-- Github.com: Containernetworking: CNI

Your CNI plugin in simple terms is responsible for pod's networking inside your cluster.

There are multiple CNI plugins like:

• Flannel
• Calico
• Multus
• Weavenet

What I mean about that, you don't need to use Flannel. You can use other plugin like Calico. The major consideration is that they are different from each other and you should pick option best for your use case (support for some feature for example).

There are a lot of materials/resources on this topic. Please take a look at some of them:

• Youtube.com: Kubernetes and the CNI: Where We Are and What's Next - Casey Callendrello, CoreOS
• Youtube.com: Container Network Interface (CNI) Explained in 7 Minutes
• Kubernetes.io: Docs: Concepts: Cluster administration: Networking

As for:

If Flannel is difficult to setup for mixed mode, can we use other network which can work?

If you mean mixed mode by using nodes that are Windows and Linux machines, I would stick to guides that are already written like one you mentioned: Kubernetes.io: Adding Windows nodes

As for:

If we decide to go only and only RHEL nodes, what is the best and easiest network plugin I can install without going through lot of issues?

The best way to choose CNI plugin would entail looking for solution fitting your needs the most. You can follow this link for an overview:

• Kubernetes.io: Docs: Concepts: Cluster administration: Networking

Also you can look here (Please have in mind that this article is from 2018 and could be outdated):

• Itnext.io: Benchmark results of Kubernetes network plugin cni over 10gbit's network

when I go to my RHEL worker node, I see that k8s_install-cni_kube-flannel-ds-amd64-f4mtp_kube-system container is exited as seen below:

Your k8s_install-cni_kube-flannel-ds-amd64-f4mtp_kube-system container exited with status 0 which should indicate correct provisioning.

You can check the logs of flannel pods by invoking below command:

• kubectl logs POD_NAME

You can also refer to official documentation of Flannel: Github.com: Flannel: Troubleshooting

As I said in the comment:

To check if your CNI is working you can spawn 2 pods on 2 different nodes and try make a connection between them (like ping them).

Steps:

• Spawn pods
• Check their IP addresses
• Exec into pods
• Ping

Below is example deployment definition that will spawn ubuntu pods. They will be used to check if pods have communication between nodes: