eks

I'm trying to apply node labels using the following configuration:

  - name: test
    instanceType: m5.large
    minSize: 1
    maxSize: 2
    desiredCapacity: 2
    labels:
      role: test
      node-role.kubernetes.io/test: ok

According to #580 and #582 using node-role subdomain should the way to apply labels, however I still get a domain error:

AWS::EKS::No

What would you like to be added:
Cilium is our default CNI solution on EKS-A clusters. It would be beneficial to enable Cilium metrics so that existing Prometheus could be configured to scrape those targets.

NTH Queue-Processor should catch the ASG Launch Lifecycle Hook and complete it once the node has joined the k8s cluster successfully. Since ASG considers the instance ready when EC2 health checks pass rather than when it actually joins the k8s cluster, if ASG performs Launch-Before-Terminate, a node could be terminated before the new node is ready to go.

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem

The kiali-operator may require higher memory limits for clusters with bigger amount of nodes. Thus resource limits shall be configurable via values.

Describe the solution you'd like A clear and concise description of what you want to happen.
Enrich schema for Kiali-operator

Some log entries are using V(1) but still get emitted by default.
We should have a way to mute debug logs using a flag.