ns-tools | Convenience Tools for working with NativeScript | Mobile library

This error was due to different cxf jar versions being used This was solved by matching all the cxf versions in the pom.xml. of current project and all the projects being imported.

As posted in the comments:

Please add to the question the steps that you followed (editing any values in the Helm chart etc). Also please check if the nodes are not over the limit of pods that can be scheduled on it. Here you can find the link for more reference: LINK.

no processes occupying 9100 on the given node. @DawidKruk The POD limit was reached. Thanks! I expected them to give me some error regarding that rather than vague node selector property not matching

Not really sure why the following messages were displayed:

• node(s) didn't have free ports for the requested pod ports
• node(s) didn't match node selector

The issue that Pods couldn't be scheduled on the nodes (Pending state) was connected with the Insufficient pods message in the $ kubectl get events command.

Above message is displayed when the nodes reached their maximum capacity of pods (example: node1 can schedule maximum of 30 pods).

More on the Insufficient Pods can be found in this github issue comment:

That's true. That's because the CNI implementation on EKS. Max pods number is limited by the network interfaces attached to instance multiplied by the number of ips per ENI - which varies depending on the size of instance. It's apparent for small instances, this number can be quite a low number.

Docs.aws.amazon.com: AWSEC2: User Guide: Using ENI: Available IP per ENI

-- Github.com: Kubernetes: Autoscaler: Issue 1576: Comment 454100551

Additional resources:

• Stackoverflow.com: Questions: Pod limit on node AWS EKS

This problem is due to a bug in version 3.3.0 of the plugin. See https://github.com/ewerk/gradle-plugins/issues/89.

The bug has been fixed, so all that needs to be done in the POM.XML file is change the version number from 3.3.0 to 3.3.1:

There is no exact time for the AD Connect release of this feature.

If you want to know that as soon as possible after its release, you could trace the Azure AD Connect release history.

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/reference-connect-version-history

NoClassDefFoundError: Could not initialize class org.apache.cxf.attachment.AttachmentUtil means that JVM failed to initialize the AttachmentUtil class.

Apache CXF 3.3.X should support JDK 11 as per FAQ. You want to debug the startup with exception breakpoint on the NoClassDefFoundError exception and see what was the root cause. It looks likely a static field or block failed to run when loading AttachmentUtil class but the root cause was surpressed.