https://issues.redhat.com/browse/ACM-29840#8605
https://issues.redhat.com/browse/ACM-29840#8605dockerymick wants to merge 3 commits into2.16_stagefrom
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dockerymick The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
| ---- | ||
|
|
||
| . List the resources in the allow (`data.AllowedResources`) and deny list (`data.DeniedResources`) sections within the config map. Your config map might resemble the following YAML file: | ||
| . List the resources in the allow (`data.AllowedResources`) and deny list (`data.DeniedResources`) sections within the config map. |
There was a problem hiding this comment.
This should be rewritten so that we don't have the spec in parenthesis, not sure how that passed peer review the first time.
|
|
||
| . List the resources in the allow (`data.AllowedResources`) and deny list (`data.DeniedResources`) sections within the config map. Your config map might resemble the following YAML file: | ||
| . List the resources in the allow (`data.AllowedResources`) and deny list (`data.DeniedResources`) sections within the config map. | ||
| .. Collect `services` and `pods` from all `apiGroups`, while also collecting allowing all resources from the `admission.k8s.io` and `authentication.k8s.io` `apiGroups`. |
There was a problem hiding this comment.
Here if we are coding these, we need to name what they are. Or don't code.
| . List the resources in the allow (`data.AllowedResources`) and deny list (`data.DeniedResources`) sections within the config map. Your config map might resemble the following YAML file: | ||
| . List the resources in the allow (`data.AllowedResources`) and deny list (`data.DeniedResources`) sections within the config map. | ||
| .. Collect `services` and `pods` from all `apiGroups`, while also collecting allowing all resources from the `admission.k8s.io` and `authentication.k8s.io` `apiGroups`. | ||
| .. Configure your config map to prevent the central collection of `secrets` from all `apiGroups`, while preventing the collection of `policies`, `iampolicies`, and `certificatepolicies` from the `apiGroup` `admission.k8s.io`. |
There was a problem hiding this comment.
I will pick up on this in a sec.
There was a problem hiding this comment.
We kinda need to do the same with all of these, in that we typically don't just use the spec without naming it but I understand that would mean a lot of unnecessary rewrite. Recommend:
Configure your config map to prevent the central collection of secrets from all apiGroups specifications, while preventing the collection of policies, iampolicies, and certificatepolicies from the apiGroup admission.k8s.io specification.
| ---- | ||
|
|
||
| . List the resources in the allow (`data.AllowedResources`) and deny list (`data.DeniedResources`) sections within the config map. Your config map might resemble the following YAML file: | ||
| . List the resources in the allow (`data.AllowedResources`) and deny list (`data.DeniedResources`) sections within the config map. |
There was a problem hiding this comment.
| . List the resources in the allow (`data.AllowedResources`) and deny list (`data.DeniedResources`) sections within the config map. | |
| . List the resources in the `data.AllowedResources` and the `data.DeniedResources` fields within the config map. |
|
|
||
| . List the resources in the allow (`data.AllowedResources`) and deny list (`data.DeniedResources`) sections within the config map. Your config map might resemble the following YAML file: | ||
| . List the resources in the allow (`data.AllowedResources`) and deny list (`data.DeniedResources`) sections within the config map. | ||
| .. Collect `services` and `pods` from all `apiGroups`, while also collecting allowing all resources from the `admission.k8s.io` and `authentication.k8s.io` `apiGroups`. |
There was a problem hiding this comment.
| .. Collect `services` and `pods` from all `apiGroups`, while also collecting allowing all resources from the `admission.k8s.io` and `authentication.k8s.io` `apiGroups`. | |
| .. Collect services and pods from all `apiGroups`, while also collecting all resources from the `admission.k8s.io` and `authentication.k8s.io` `apiGroups`. |
| - iampolicies | ||
| - certificatepolicies | ||
| ---- | ||
| *Note:* If you do not provide a config map, all resources are collected by default. When you specify `AllowedResources`, all other resources are automatically excluded. If you list resources in both `AllowedResources` and `DeniedResources`, it is excluded from the collection. |
There was a problem hiding this comment.
| *Note:* If you do not provide a config map, all resources are collected by default. When you specify `AllowedResources`, all other resources are automatically excluded. If you list resources in both `AllowedResources` and `DeniedResources`, it is excluded from the collection. | |
| *Note:* If you do not provide a config map, all resources are collected by default. When you specify `AllowedResources`, all other resources are automatically excluded. If you list resources in both the `AllowedResources` and `DeniedResources` specifications, it is excluded from the collection. |
There was a problem hiding this comment.
And then what is "it" in "it is excluded" -- that should be replaced with what it is to reduce confusion.
| - iampolicies | ||
| - certificatepolicies | ||
| ---- | ||
| *Note:* If you do not provide a config map, all resources are collected by default. When you specify `AllowedResources`, all other resources are automatically excluded. If you list resources in both `AllowedResources` and `DeniedResources`, it is excluded from the collection. |
There was a problem hiding this comment.
And then what is "it" in "it is excluded" -- that should be replaced with what it is to reduce confusion.
also removed callouts from the file