Due to the complexity of the setup, ingress support in draft was removed in favour of draft connect (see Azure/draft#573). In 0.12.0 and above, it's recommended in the documentation to use draft connect as it initiates a tunnel straight to all the pods without needing to set up ingress controllers, DNS, etc. Are there plans to eventually migrate over, or are there limitations with the current

Describe the bug
When looking to understand how to correlate task create --set name=value with a tasks.yaml that parses .Values.name we don't have any doc examples.

To Reproduce
Steps to reproduce the behavior:

1. Multi-step tasks references --set name=value
2. [Tasks Referen

• Instructions as specified do not work with 1.x version of operator .
  -- missing instructions to create service account and associating the cluster role with service account
• The .yaml files referred to in the instructions are not available in the s3 bucket. Instructions to be updated to refer to ones t

• Waiting for https://github.com/Azure/aks-engine/projects/7
• https://github.com/aquasecurity/kube-bench
• Azure/AKS#367
• https://github.com/sabbour/kube-bench-aks/blob/master/cfg/1.11/config.yaml
• https://blog.aquasec.com/kubernetes-security-cis-benchmarks

kubectl run --rm -i -t kube-bench-node --image=sabbour/kube-bench-aks:latest --restart=Never --overri