Martin Emrich

The change definitely has not the intended effect for more than a few minutes, even stripping out other optional features does not. So I cancel this, sorry to bother...

@ndbaker1 TBH #2224 solved it in the worst way possible: Building a whole own AMI with "custom stuff" in there, and they will have to repeat that regularly to keep...

Thanks! If you want I can keep this open for the specific feature of setting sysctls, otherwise I would close it.

For anyone flying by via Google, this (in eksctl ClusterConfig managedNodeGroup) worked: ``` preBootstrapCommands: - 'echo "kernel.sysrq = 1" > /etc/sysctl.d/magicsysrq.conf' - 'echo 1 > /proc/sys/kernel/sysrq' ```

@NicholasBlaskey TBH I do not know, but usually this is one of these jobs I send off in a terminal, do something else, and check back around >30min later. As...

@matheuscscp yes, until now, this policy was implicitly available on the NodeInstanceRole. Now one has to give it explicitly to source-controller (one way or another).

Yes, the node instance role is assigned by the user on each managed node group, there's no general AWS default, only a recommendation (which is that new ...PullOnly Policy): https://docs.aws.amazon.com/eks/latest/userguide/create-node-role.html...

+1 I thought it was as simple as ``` ... spec: mariaDbRef: name: xxx config: params: enable_root_user: "1" replicas: 3 affinity: ... ``` But it crashes and I get: ```...