-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Improve vendor fork experience #267
Comments
I think the main outstanding item here is configure the helm chart for new vendors. |
Do you mean documenting this? |
That link isn't redirecting properly for me so not sure. But at least have something like this documented for kubernetes |
I'd be curious if vendors would like more specific documentation around forking + maintaining too. Microsoft doesn't have a fork today so I don't have a lived perspective |
What I meant to share was the comment on slack by @puckpuck showing how to use helm to deploy the demo and configure the collector to a specific vendor |
I can take a first stab at documenting the fork process this week. |
From my perspective the key part will be documenting the options available via custom a custom values file. That covers all of the use cases Instana will need for our fork. |
Yeah that'd be great to get @joshleecreates |
Thanks for taking care of this Josh! |
Vendors need proper documentation and repo improvements to ensure their forks aren't difficult to maintain.
The text was updated successfully, but these errors were encountered: