Jay Pipes

The root cause of this is old kernel/packages in the EKS AMI. We have created an issue in the EKS AMI repo for tracking. https://github.com/awslabs/amazon-eks-ami/issues/380 Closing this as duplicate (not...

Yup, we goofed, sorry @taylorb-syd! It is #516 and #662 that are related to the awslabs/amazon-eks-ami#380

@bbc88ks Hi Val, would you mind letting us know if upgrading to the forward CoreDNS plugin (in the configmap) resolved your issues? (pun intended) Thanks, and sorry for the delay...

related: https://github.com/awsdocs/amazon-eks-user-guide/pull/72

@mentalisttraceur apologies for the long delay in responding here. How do you determine that the reason the daemonset goes into CrashLoopBackoff is due to improper IAM role permissions? I presume...

@mentalisttraceur can you provide a snippet of your logs before and after adding the IAM role so that we can determine what is not being logged or reported as an...

The deliverable here is to test specifically what happens when you deploy the aws-node daemonset and have improper IAM role permissions. We need to document what this looks like from...

Unfortunately, it looks like the name of the queue is hardcoded as the Kubernetes cluster name + "-cloudformation": https://github.com/awslabs/aws-service-operator/blob/b2a8a4ee29dbcedb38c5e310dd8ca103792ac62f/cmd/aws-service-operator/main.go#L136 @nomis-rzp we are refactoring the AWS Service Operator and are not...

@ryansteakley @surajkota seems fairly straightforward and similar to `TrainingJob` to me... Ryan, did you need assistance generating the resource manager for `PipelineExecution` resources?

@brycahta I agree that using resource references would be the best user experience here. Potentially also removing the `groupName` field entirely since it's only used for EC2 Classic...