Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate Club Manager and Jukebox k8s configs to separate namespaces #46

Open
2 tasks
IkeHunter opened this issue Feb 7, 2025 · 1 comment
Open
2 tasks
Labels
k8s You'll be working with Kubernetes

Comments

@IkeHunter
Copy link
Collaborator

Info

Currently, the jukebox and club manager k8s config are in the same "main" namespace. They should be separated into namespaces like this:

  • Club Manager (& proxy): main
  • Jukebox: jukebox

You will potentially come across issues with connecting the proxy to jukebox server (& its websocket), you will probably need to change the references to the Jukebox Server in the proxy config to update the namespaces.

Tasks

  • Split jukebox resources to namespace called jukebox
  • Fix all broken references to the jukebox server and/or websocket
@IkeHunter IkeHunter added the k8s You'll be working with Kubernetes label Feb 7, 2025
@IkeHunter
Copy link
Collaborator Author

@Ryan-slither

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
k8s You'll be working with Kubernetes
Projects
None yet
Development

No branches or pull requests

1 participant