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

Helm vs k8s operator #645

Closed
scobit opened this issue Jan 14, 2025 · 2 comments
Closed

Helm vs k8s operator #645

scobit opened this issue Jan 14, 2025 · 2 comments
Labels
untriaged Issues that have not yet been triaged

Comments

@scobit
Copy link

scobit commented Jan 14, 2025

Hello!

I'm planning to use Opensearch to get logs from k8s cluster.

I have some experience with Elasticsearch solution, and their Helm distribution currently in archive status. As I understand it's hard to maintain both solutions (Helm and k8s Operator).

So I'd like to ask about Helm project status. Is there any plans to stop maintain both solutions and focus on k8s operator?

@DandyDeveloper
Copy link
Collaborator

@scobit These are mostly managed through different individuals and most are contributors / volunteers. Operator and Helm sides are actually managed by different individuals, I don't think we have cross-over between the maintainers.

That is it say, I think this will be maintained as long as these people exist. I know some members of AWS are committed to the Helm side, as well as the operator.

The Helm solution is still solid for almost all use cases, so I don't see it going anywhere anytime soon.

@scobit
Copy link
Author

scobit commented Jan 16, 2025

@DandyDeveloper Thank you.

@scobit scobit closed this as completed Jan 16, 2025
@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Engineering Effectiveness Board Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
untriaged Issues that have not yet been triaged
Projects
Status: ✅ Done
Development

No branches or pull requests

2 participants