Resolve "Integrate bb-common"
General MR
Summary
This MR configures the minio package to use bb-common for generating Istio and NetworkPolicy resources. Some NetworkPolicy and AuthorizationPolicy resources simply were not necessary for the package to function and have been removed. If the reviewer is aware of a reason why one or more of these policies should be reinstated, please let me know.
Umbrella Branch
minio-186-integrate-bb-common
Relevant logs/screenshots
Basic Functionality
Console access
API access
❯ curl https://minio-api.dev.bigbang.mil/
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>AccessDenied</Code><Message>Access Denied.</Message><Resource>/</Resource><RequestId>188A638E70555F8D</RequestId><HostId>08f1eaefb69c6c4334905881bb8e2f8c9ad66fc60be3f139253bf66b089e248a</HostId></Error>
Velero Backup
Creating backups
❯ kubectl -n velero exec -it deployments/velero -n velero -- bash
bash-5.1$ /velero backup create goodbackup
Backup request "goodbackup" submitted successfully.
Run `velero backup describe goodbackup` or `velero backup logs goodbackup` for more details.
bash-5.1$ /velero backup create monitoringbackup --include-namespaces=monitoring
Backup request "monitoringbackup" submitted successfully.
Run `velero backup describe monitoringbackup` or `velero backup logs monitoringbackup` for more details
Validating backups completed successfully
❯ kubectl get backups.velero.io -A -o yaml | yq '[.items[].status]'
- completionTimestamp: "2026-01-13T20:25:54Z"
expiration: "2026-02-12T20:25:31Z"
formatVersion: 1.1.0
hookStatus: {}
phase: Completed
progress:
itemsBackedUp: 6417
totalItems: 6417
startTimestamp: "2026-01-13T20:25:31Z"
version: 1
warnings: 14
- completionTimestamp: "2026-01-13T20:25:59Z"
expiration: "2026-02-12T20:25:54Z"
formatVersion: 1.1.0
hookStatus: {}
phase: Completed
progress:
itemsBackedUp: 437
totalItems: 437
startTimestamp: "2026-01-13T20:25:54Z"
version: 1
Backups in object browser in minio console
Linked Issue
Upgrade Notices
The minio package has been migrated to bb-common. While steps have been taken to maintain backwards compatibility with existing configurations by translating the old configuration into bb-common's more explicit syntax, Big Bang consumers are encouraged to migrate their values directly as soon as possible. Some appropriate configuration changes when consumers migrate are outlined below.
Ingress Config
bb-common creates a consistent ingress configuration syntax across all Big Bang packages with its routes functionality. Take a look at the routes documentation to understand how to use it to expose various minio services.

