Tim Schwenke

I'm just using local exec to deploy the few Kubernetes resources I want to "manage" with Terraform. At the moment I don't want to split my rather small Terraform state...

Does any of the syntaxes work for you? 

@konstantinbarkalov, how can I turn it on? When I login with config password it fails on import: 

Ok I logged into the server created the file `file.ldif` ``` dn: cn=module{0},cn=config changetype: modify add: olcModuleLoad olcModuleLoad: pw-sha2 - ``` And then executed following command: ``` ldapmodify -Q -Y...

@bliles, I don't agree with this statement. At my company (and probably we aren't the only ones) our AWS accounts all enforce that every role must trust a specific entity...

Can't you just use `docker_machine_iam_policy_arns`?

Also it is useful for me because in the accounts I work with rules enforce that every role must trust a special entity used for monitoring and audit

A major version bump that throws out a bunch of deprecated stuff would be great

There's another gotcha. WSL automatically adds stuff to PATH pointing to windows directories. This can bring auto complete to a hold. Solution: disabling this part of auto complete or disabling...

Is this still relevant? We now have a benchmark optimized for EKS. ```txt sh-4.2$ kube-bench run --targets node --benchmark eks-1.0.1 [INFO] 3 Worker Node Security Configuration [INFO] 3.1 Worker Node...