deletes the bgutil-pot-provider ImageRepository/ImagePolicy and its README row
Both owning Kustomizations (music-assistant, infrastructure) have prune: true, so Flux removes the live objects on merge. No other references remain (grep -rn 'po-token\|bgutil' kubernetes/ is empty); both kustomizations render.
The YouTube Music provider itself lives in MA's settings.json and is removed in the MA UI.
Reverts #1451. The YouTube Music provider is not kept, so the PO token server goes:
- deletes `kubernetes/apps/music-assistant/po-token-server.yaml` (Deployment, Service, CNP)
- deletes the `bgutil-pot-provider` ImageRepository/ImagePolicy and its README row
Both owning Kustomizations (`music-assistant`, `infrastructure`) have `prune: true`, so Flux removes the live objects on merge. No other references remain (`grep -rn 'po-token\|bgutil' kubernetes/` is empty); both kustomizations render.
The YouTube Music provider itself lives in MA's settings.json and is removed in the MA UI.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Reverts #1451. The YouTube Music provider is not kept; the PO token
server and its image automation go with it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🤖Automated review — model claude-sonnet-5-5, commit 0f86537bb133a9d51b5fbc32eabe183aa560ac9c.
Automated review by the review-bot: it approves only when it found nothing red or yellow, and a human still merges. Push new commits to get a fresh review.
Summary
This PR reverts the commit that added the PO token server (96ea510). It deletes po-token-server.yaml (Deployment, Service, CNP) and the bgutil-pot-provider ImageRepository/ImagePolicy. It also removes their entries from both kustomizations and the README row. The diff is the exact inverse of 96ea510: the same five files change and the content matches line for line. I found nothing wrong with it.
Checks:
The PR is mergeable and based on main at 31459da. Nothing on the base touches these files after 96ea510, so there is no conflict and no overlap with another change.
The remaining kubernetes/apps/music-assistant/kustomization.yaml and kubernetes/infrastructure/image-automation/kustomization.yaml at the head sha no longer list the deleted files.
deployment.yaml for music-assistant has no reference to po-token-server, port 4416 or bgutil. No other CNP or env var depends on the removed Service.
The PR has no earlier reviews or comments, so this is a first review.
⚪ Unverified
The PR says a repo-wide grep -rn 'po-token\|bgutil' kubernetes/ is empty. I could not run grep with the tools I have. I read the music-assistant directory and both kustomizations, and an issue and PR search for "po-token" only returned this PR. I did not read every file in the repo.
prune: true on the owning Kustomizations is taken from the PR body. I did not open the Flux Kustomization manifests. If prune were off, the live Deployment, Service, CNP, ImageRepository and ImagePolicy would stay behind as orphans.
Tests
No tests apply. This is a manifest-only removal, and the PR says both kustomizations still render.
Recommendation
Looks reasonable — no blocking issues.
🤖 **Automated review** — model `claude-sonnet-5-5`, commit `0f86537bb133a9d51b5fbc32eabe183aa560ac9c`.
> Automated review by the `review-bot`: it approves only when it found nothing red or yellow, and a human still merges. Push new commits to get a fresh review.
---
## Summary
This PR reverts the commit that added the PO token server (96ea510). It deletes `po-token-server.yaml` (Deployment, Service, CNP) and the `bgutil-pot-provider` ImageRepository/ImagePolicy. It also removes their entries from both kustomizations and the README row. The diff is the exact inverse of 96ea510: the same five files change and the content matches line for line. I found nothing wrong with it.
Checks:
- The PR is mergeable and based on `main` at 31459da. Nothing on the base touches these files after 96ea510, so there is no conflict and no overlap with another change.
- The remaining `kubernetes/apps/music-assistant/kustomization.yaml` and `kubernetes/infrastructure/image-automation/kustomization.yaml` at the head sha no longer list the deleted files.
- `deployment.yaml` for music-assistant has no reference to `po-token-server`, port 4416 or bgutil. No other CNP or env var depends on the removed Service.
- The PR has no earlier reviews or comments, so this is a first review.
## ⚪ Unverified
- The PR says a repo-wide `grep -rn 'po-token\|bgutil' kubernetes/` is empty. I could not run grep with the tools I have. I read the music-assistant directory and both kustomizations, and an issue and PR search for "po-token" only returned this PR. I did not read every file in the repo.
- `prune: true` on the owning Kustomizations is taken from the PR body. I did not open the Flux Kustomization manifests. If prune were off, the live Deployment, Service, CNP, ImageRepository and ImagePolicy would stay behind as orphans.
## Tests
No tests apply. This is a manifest-only removal, and the PR says both kustomizations still render.
## Recommendation
Looks reasonable — no blocking issues.
<!-- pr-review:sha=0f86537bb133a9d51b5fbc32eabe183aa560ac9c -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Reverts #1451. The YouTube Music provider is not kept, so the PO token server goes:
kubernetes/apps/music-assistant/po-token-server.yaml(Deployment, Service, CNP)bgutil-pot-providerImageRepository/ImagePolicy and its README rowBoth owning Kustomizations (
music-assistant,infrastructure) haveprune: true, so Flux removes the live objects on merge. No other references remain (grep -rn 'po-token\|bgutil' kubernetes/is empty); both kustomizations render.The YouTube Music provider itself lives in MA's settings.json and is removed in the MA UI.
🤖 Generated with Claude Code
🤖 Automated review — model
claude-sonnet-5-5, commit0f86537bb133a9d51b5fbc32eabe183aa560ac9c.Summary
This PR reverts the commit that added the PO token server (
96ea510). It deletespo-token-server.yaml(Deployment, Service, CNP) and thebgutil-pot-providerImageRepository/ImagePolicy. It also removes their entries from both kustomizations and the README row. The diff is the exact inverse of96ea510: the same five files change and the content matches line for line. I found nothing wrong with it.Checks:
mainat31459da. Nothing on the base touches these files after96ea510, so there is no conflict and no overlap with another change.kubernetes/apps/music-assistant/kustomization.yamlandkubernetes/infrastructure/image-automation/kustomization.yamlat the head sha no longer list the deleted files.deployment.yamlfor music-assistant has no reference topo-token-server, port 4416 or bgutil. No other CNP or env var depends on the removed Service.⚪ Unverified
grep -rn 'po-token\|bgutil' kubernetes/is empty. I could not run grep with the tools I have. I read the music-assistant directory and both kustomizations, and an issue and PR search for "po-token" only returned this PR. I did not read every file in the repo.prune: trueon the owning Kustomizations is taken from the PR body. I did not open the Flux Kustomization manifests. If prune were off, the live Deployment, Service, CNP, ImageRepository and ImagePolicy would stay behind as orphans.Tests
No tests apply. This is a manifest-only removal, and the PR says both kustomizations still render.
Recommendation
Looks reasonable — no blocking issues.