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

Adapt Beekeeper for in-cluster deployment via Kubernetes services #418

Closed
gacevicljubisa opened this issue Oct 10, 2024 · 1 comment · Fixed by #439
Closed

Adapt Beekeeper for in-cluster deployment via Kubernetes services #418

gacevicljubisa opened this issue Oct 10, 2024 · 1 comment · Fixed by #439
Assignees

Comments

@gacevicljubisa
Copy link
Contributor

gacevicljubisa commented Oct 10, 2024

Ensure that Beekeeper can work through Kubernetes services when the relevant flag is set, allowing internal communication within the cluster, not just through ingress. This includes:

  • Modification of the Beekeeper k8s package.
  • Updating Beekeeper's configuration to support communication via Kubernetes services.
  • Testing and validating the new setup within the Kubernetes cluster.

Acceptance Criteria:

  • Beekeeper successfully communicates with other components via Kubernetes services when the flag is set.

Requested by: @darkobas2

@gacevicljubisa gacevicljubisa self-assigned this Oct 10, 2024
@darkobas2
Copy link

Low priority, i have made a dns work around

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants