Giters

aws / aws-network-policy-agent

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

vpc cni - aws-eks-nodeagent log clarification

shabbskagalwala opened this issue · comments

commented

What happened:

I recently upgraded one of my homelab clusters to 1.25 from 1.24 and am seeing log messages from the aws-eks-nodeagent sidecar on the aws-node daemonset

✗ k logs -f -n kube-system -c aws-eks-nodeagent aws-node-fczsz
{"level":"info","ts":"2023-10-18T20:40:52.456Z","caller":"runtime/asm_amd64.s:1598","msg":"version","GitVersion":"","GitCommit":"","BuildDate":""}
2023-10-18 20:40:52.462361271 +0000 UTC Logger.check error: failed to get caller
2023-10-18 20:40:52.462410354 +0000 UTC Logger.check error: failed to get caller

Everything looks good the nodes are ready, the pods seem to be working fine. But just not sure what this error log means and if it is of any concern.

Note: This add on is a managed add on and not installed manually.

      - args:
        - --enable-ipv6=false
        - --enable-network-policy=false
        - --enable-cloudwatch-logs=false
        - --enable-policy-event-logs=false
        - --metrics-bind-addr=:8162
        - --health-probe-bind-addr=:8163

From some previous issues I did see that the network policy not being set was the issue but that arg is being set.

Seeing this on add on versions

v1.15.1-eksbuild.1
v1.15.3-eksbuild.1

Also these are all the CRD's installed based on previous issues

✗ k get crd | grep -i aws
cninodes.vpcresources.k8s.aws                2023-08-16T21:57:48Z
eniconfigs.crd.k8s.amazonaws.com             2023-05-24T17:15:19Z
ingressclassparams.elbv2.k8s.aws             2023-05-24T18:34:32Z
policyendpoints.networking.k8s.aws           2023-09-07T22:11:39Z
securitygrouppolicies.vpcresources.k8s.aws   2023-05-24T17:15:21Z
targetgroupbindings.elbv2.k8s.aws            2023-05-24T18:34:33Z

Configuration on the managed add on

{"env":{"MINIMUM_IP_TARGET":"10","WARM_ENI_TARGET":"0","WARM_IP_TARGET":"2"}}

Please let me know if i can provide any further information. Thank you!

Environment:

  • Kubernetes version (use kubectl version):
✗ kubectl version --short
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
Client Version: v1.26.2
Kustomize Version: v4.5.7
Server Version: v1.25.15-eks-4f4795d
  • CNI Version: v1.15.1-eksbuild.1 and v1.15.3-eksbuild.1
commented

Those logs are not of any concern. It is coming from the zap logger utility. We will fix it to avoid any such confusions.

commented

@jayanthvn got it - thank you for confirming! That answers my question. Closing this 👍