Follow the [bb-common Migration Guide](https://repo1.dso.mil/big-bang/product/packages/bb-common/-/tree/main/docs/network-policies?ref_type=heads#migration-guide) to integrate bb-common into package. <table> <tr> <th>Old Name</th> <th>New Name</th> <th>Notes</th> <th>Covered in bb-common</th> </tr> <tr> <td>allow-alloy-ingress-mimir-mimir</td> <td></td> <td> Following the lead here, as I noticed it was a little weird as well: [Draft: Mimir allow alloy metrics (](https://repo1.dso.mil/big-bang/product/packages/mimir/-/merge_requests/80/diffs?commit_id=7655872ec9fc67e5d45b1071d7428226c5942529)!80[) · Merge requests · Big Bang / Universe / Product / mimir · GitLab](https://repo1.dso.mil/big-bang/product/packages/mimir/-/merge_requests/80/diffs?commit_id=7655872ec9fc67e5d45b1071d7428226c5942529) </td> <td>No</td> </tr> <tr> <td>allow-dns-lookups-mimir</td> <td>default-egress-allow-kube-dns</td> <td></td> <td>Yes</td> </tr> <tr> <td>allow-egress-storage-mimir-mimir</td> <td>allow-egress-from-mimir-to-anywhere-tcp-port-443</td> <td>This is a 443 egress to any IP.</td> <td></td> </tr> <tr> <td>allow-in-namespace-mimir-mimir</td> <td> default-ingress-allow-all-in-ns default-egress-allow-all-in-ns </td> <td></td> <td>Yes</td> </tr> <tr> <td>allow-istiod-egress-mimir-mimir</td> <td>default-egress-allow-istiod</td> <td></td> <td>Yes</td> </tr> <tr> <td>allow-kube-apiserver-egress-mimir-mimir</td> <td> allow-egress-from-mimir-to-kubeapi allow-egress-from-minio-to-kubeapi allow-egress-from-rollout-operator-to-kubeapi </td> <td>Put definition override in umbrella chart, and use the definition in the mimir package.</td> <td>No</td> </tr> <tr> <td>allow-mimir-egress-grafana</td> <td>allow-egress-from-mimir-to-ns-monitoring-pod-grafana-tcp-port-3000</td> <td>Will need ingress rule on the grafana side. Mirror this egress rule to the ingress rule for grafana, both in umbrella chart.</td> <td>No</td> </tr> <tr> <td>allow-mimir-egress-minio</td> <td>N/A</td> <td>Removed this, as there is nothing in the helmrelease that shows a dependency for the minio namespace.</td> <td>No</td> </tr> <tr> <td>allow-mimir-ingress-grafana</td> <td> allow-ingress-to-mimir-tcp-ports-8080-9095-from-ns-monitoring-pod-grafana allow-ingress-to-rollout-operator-tcp-ports-8080-9095-from-ns-monitoring-pod-grafana </td> <td>mimir is in it's own namespace, seperate from grafana, this should not be here?</td> <td></td> </tr> <tr> <td>allow-mimir-sidecar-scraping</td> <td> allow-ingress-to-mimir-tcp-port-15020-from-ns-monitoring-pod-prometheus allow-ingress-to-minio-tcp-port-15020-from-ns-monitoring-pod-prometheus allow-ingress-to-rollout-operator-tcp-port-15020-from-ns-monitoring-pod-prometheus </td> <td></td> <td></td> </tr> <tr> <td>allow-mimir-test-egress</td> <td>N/A</td> <td>No longer needed with newer versions of gluon.</td> <td></td> </tr> <tr> <td>allow-minio-egress-minio</td> <td>N/A</td> <td>Did not add this one back in. This seems like all internal namespace traffic.</td> <td></td> </tr> <tr> <td>allow-minio-ingress-mimir</td> <td>N/A</td> <td>Did not add this one back in. This seems like all internal namespace traffic.</td> <td></td> </tr> <tr> <td>allow-prometheus-ingress-mimir-mimir</td> <td> allow-ingress-to-mimir-tcp-ports-8080-9095-from-ns-monitoring-pod-prometheus allow-ingress-to-rollout-operator-tcp-ports-8080-9095-from-ns-monitoring-pod-prometheus allow-ingress-to-minio-tcp-port-9000-from-ns-monitoring-pod-prometheus </td> <td></td> <td></td> </tr> <tr> <td>default-deny-all-mimir-mimir</td> <td> default-ingress-deny-all default-egress-deny-all </td> <td></td> <td>Yes</td> </tr> <tr> <td>minio-operator-egress</td> <td>N/A</td> <td> I don't see anything named minioOperator. Is this needed/doing anything? I don't see the 4222 service or the app with a name minioOperator. {width="547" height="42"} {width="401" height="54"} </td> <td></td> </tr> <tr> <td>minio-operator-ingress</td> <td>allow-ingress-to-minio-tcp-port-9000-from-ns-minio-operator-pod-minio-operator</td> <td>I don't see anything named minioOperator. Added new policy to fix connectivity.</td> <td></td> </tr> </table>