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

Advice about deploying #12

Open
istathar opened this issue Mar 15, 2023 · 2 comments
Open

Advice about deploying #12

istathar opened this issue Mar 15, 2023 · 2 comments
Labels
type: discussion Requests for comments, discussions about possible enhancements.

Comments

@istathar
Copy link

Hello! Do you have any advice about how best to deploy this to a cluster? Should it (for example) be integrated into the honeycomb-agent's Helm chart?

Does it have to be in a particular namespace to see the control plane events?

Presumably it is meant to be a DeamonSet; a sample object of what resources it was given to run would be terrific!

@istathar istathar added the type: discussion Requests for comments, discussions about possible enhancements. label Mar 15, 2023
@mr-ransel
Copy link

I don't believe this would be a DaemonSet, just a standalone pod, with the necessary ServiceAccount, ClusterRole, and ClusterRoleBindings created (although I'm still trying to work out the minimum necessary permissions), because as I understand it kspan is collecting events directly from the API, not the nodes, so only a single instance per cluster is required. Unless you're already running a otel collector service, you'll need to specify an otlp address as well. I'm currently working through trying to get this set up myself, so happy to be corrected by someone who's already done it.

@patrickdung
Copy link

Guys, I created two separate namespaces for kspan and jaeger and is able to use the kspan.

Please refer to my article for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: discussion Requests for comments, discussions about possible enhancements.
Projects
None yet
Development

No branches or pull requests

3 participants