It'd be helpful if there was a check for ELB and ALBs that have either no listeners or no instances in their target pool. The check is similar to an unused security group although their are more financial penalties for having idle ELB and ALBs.

I've been tasked with creating a CIS Level 1 standard RHEL image in Azure. I've taken a market place RHEL 7.3 image and applied this playbook with packer/ansible using tags level1.

However, when I go and try and create a VM from the image, it fails. If I skip cis_section1, I can create a VM from the image. I'm a linux newbie, apologies, but any obvious rules in section 1 that could be causing

The link to the CIS guide doesn't work anymore.

On their current version of this it, the ubuntu 16 guide is hidden behind an email registration here: https://www.cisecurity.org/benchmark/ubuntu_linux/

The page is branded for Ubuntu 18, and has a back link for Ubuntu 14, but if you register, you get an email with a link to a download archive where Ubuntu the Ubuntu 16 PDF is available.

Each bug report comes with a unique file that was used to generate the error. We should place these files in the test folder and include them in the CI pipeline as a form of regression testing.

At the same time it would be nice to look over the example files and ensure those in the file are truly 'exemplar'.

Issue

I deployed a kubernetes-core cluster v1.11 cluster with Conjure up on LXD.

I deployed Rancher 2 on top of K8s cluster

juju config kubernetes-worker allow-privileged=true
juju config kubernetes-master allow-privileged=true
juju config kubernetes-master authorization-mode="RBAC,Node"

wget https://raw.githubusercontent.com/CanonicalLtd/canonical-kubernetes-third-party-integrati