Alexander Yastrebov

> // briefly block cluster update to retrigger CLM Why is this needed? I think CLM will be triggered by the `update_apply_only` config item change, won't it?

:+1:

This makes sense to have only when subnets are tagged with cluster id https://github.com/zalando-incubator/kube-ingress-aws-controller/blob/6780b71333d9cbda3ca7601e4df4a25e50005013/aws/ec2.go#L193-L207

Hello. What is the controller version you are using? Could you provide a more detailed error log message?

@SarumObjects Could you get ingress controller logs as well (`kubectl logs kube-ingress-aws-controller-...`)?

Could you try to run with `--debug` option (it would print more details in the logs)? 401 suggests some kind of problem with AWS credentials.

> there's no --debug at the command line. ``` ~$ docker run -it --rm registry.opensource.zalan.do/teapot/kube-ingress-aws-controller:latest --help INFO[0000] starting /kube-ingress-aws-controller v0.12.14 usage: kube-ingress-aws-controller [] Flags: --help Show context-sensitive help (also try...

@sbueringer @alvaroaleman I guess we can close this as done?

Previous discussion https://github.com/golang/go/issues/53447

If there would be a digit alphabet-based number formatter (say `strconv.Format`) this could be expressed like: ```go strconv.Format(rand.Int64(), alphabet) + strconv.Format(rand.Int64(), alphabet) ```