-
Notifications
You must be signed in to change notification settings - Fork 231
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
Aerospike Blueprint #597
Comments
Hi @chrismld, thanks for opening the issue first. Glad to hear you are working with the partner on this. Typically for partner products we ask that they host the blueprint in a repo that's owned by them. That way they have the control over the content of the blueprint and move quickly on any changes they need to make like issues/features. On our side we are happy to add a reference on the DoEKS website that redirects visitors to a website or github repo. |
This issue has been automatically marked as stale because it has been open 30 days |
thanks @askulkarni2, we'll work with Aerospike to create the blueprint in one of their repos. I'll keep this issue open as I'll create a PR when that's ready. |
This issue has been automatically marked as stale because it has been open 30 days |
still working with Aerospike on this |
This issue has been automatically marked as stale because it has been open 30 days |
We're still working on this |
This issue has been automatically marked as stale because it has been open 30 days |
We're still working on this |
This issue has been automatically marked as stale because it has been open 30 days |
We're still working on this |
Community Note
What is the outcome that you are trying to reach?
A blueprint about how to deploy Aerospike on EKS.
Describe the solution you would like
A blueprint that uses that deploys the Aerospike operator, and guide you on how to create clusters following AWS & Aerospike best practices.
Describe alternatives you have considered
N/A
Additional context
I'm already working on this blueprint together with the Aerospike team, so expect a PR.
The text was updated successfully, but these errors were encountered: