hayden

@timmattison Hello, Can you review this PR? This commit was my best approach to solve that issue (lambda update status). I think may be there is other way to solve...

@timmattison When I first submit this PR, I didn't know that there is the lambda client waiter class in aws java sdk. So I made checking logic for last update...

@timmattison Ah, it's weird. I will check there is any problem in this code. > Does it need the waiter and the retry policy? No, It just need the waiter...

@timmattison Okay, If you need my local built image (from this branch), here is https://hub.docker.com/layers/aws-greengrass-provisioner/sktpghks1/aws-greengrass-provisioner/latest/images/sha256-d591d95694a71514f2b1deff9557852a215d468a1dbfc73af3142b748b1d44e4?context=explore

I think your code is more suitable in most cases. (create new function, update existing function). I will try this version tomorrow. Thank you.

There is no problem with creating & updating lambda with this version in my case. Thank you for your job. I use python a lot of time in my work...

Try this ``` prometheus: prometheusSpec: storageSpec: volumeClaimTemplate: spec: storageClassName: foo accessModes: - ReadWriteOnce resources: requests: storage: 30Gi ``` In my case, It works. If you missed `prometheus` the higher layer...

@hufhend Yeah, you can disable scheduling the pods to control plane with that taints. By the way, What I want to describe is seperating the `kube-apiserver` from static pods that...

@VannTen > Do you mean separating control plane components on different nodes ? Aka for instance Yes, I meant like that, additionally [kube_api_server] hosts could be `not kubernetes control plane...

> I don't think whether the api-server runs on top of kubelet as a container or directly as a systemd service is particularly impactful (and systemd can run service exactly...