When auditing is disabled by setting the `None` API server profile in the hostedcluster resource. When dealing with individual clusters this should be fine, but with how resource intensive hypershift is at scale we are trying to cut down on as many resources as possible. In this case removing 4 configmaps from each cluster would help significantly in reducing our master etcd size. For our customers, we automatically disable auditing when a cluster is created and is enabled when the customer decides to enable it.

Always reproducible

    1. Enable auditing on cluster (which is by default)
    2. Set kas audit profile to "None" through hostedcluster resource
    3. Watch audit-logs container be removed but apiserver volume/volume mounts remain in deployments and configmaps staying around.