LBC depends on cert-manager but kops can get in a circular dependency loop when applying these manifests on a new cluster.
The cert-manager pods wont be created because the LBC webhook on "CREATE pods" isn't working yet, but LBC pod cant be created because it depends on a secret volume mount created by cert-manager
By introducing a few new fields within the Cluster spec's
"awsLoadBalancerController" field, allow users to enable the AWS Load
Balancer Controller to associate WAFs with EC2 Application Load
Balancers (ALBs). It's possible to enable separately use of two kinds
of WAF: WAF Classic and the never version 2-era WAF, the latter of
which bears no distinguishing name.
Retain our default configuration of the AWS Load Balancer Controller
in which this capability remains disabled via command-line flags,
overriding the controller program's enabling of this capability by
default.
Signed-off-by: Steven E. Harris <seh@panix.com>
This commit also introduces support for adding token projection volumes for well-known SAs.
Slightly less complicated than explicitly parsing the objects for a manifest