Add application support: Elasticsearch (cluster or single node)  #472

Activity

1. dosubot

   added

   kind/featureCategorizes issue or PR as related to a new featureCategorizes issue or PR as related to a new feature

   on Nov 8, 2024
2. gecube commented on Nov 8, 2024

   

   George Gaál (gecube)

   on Nov 8, 2024

   Collaborator

   More actions

   Matthieu ROBIN (@matthieu-robin) Hi!

   Elastic like https://github.com/elastic/cloud-on-k8s
   or like https://github.com/opensearch-project/opensearch-k8s-operator

   Or it does not matter at all?

   What configuration options do you need?
3. matthieu-robin commented on Nov 8, 2024

   

   Matthieu ROBIN (matthieu-robin)

   on Nov 8, 2024

   CollaboratorAuthor

   More actions

   Hi George Gaál (@gecube) !
   Elastic prefered :-D
   Single node, cluster nodes, TLS in option could be a good start.

   Thanks a lot
4. Nick Volynkin (NickVolynkin)

   added the

   Feature

   issue type on Mar 25, 2025
5. Nick Volynkin (NickVolynkin)

   changed the title [-]Add application support : Elasticsearch ( cluster or single node) [/-] [+]Add application support: Elasticsearch (cluster or single node) [/+] on Mar 25, 2025
6. dosubot commented on Oct 18, 2025

   

   dosubotbot

   on Oct 18, 2025 – with DosuBot

   More actions

   Hi, Matthieu ROBIN (@matthieu-robin). I'm Dosu, and I'm helping the CozyStack team manage their backlog and am marking this issue as stale.

   Issue Summary:

   • You requested adding support for deploying Elasticsearch within Cozy, either as a single node or cluster.
   • The goal is to help administrators and users manage Elasticsearch instances more easily.
   • The maintainer asked for clarification on whether you prefer Elastic's official operator or OpenSearch's.
   • You confirmed a preference for Elastic's operator with features like single node, cluster nodes, and optional TLS.
   • The issue remains unresolved with no recent updates.

   Next Steps:

   • Please let me know if this feature request is still relevant to the latest version of Cozy by commenting on this issue.
   • If I don’t hear back within 7 days, I will automatically close this issue to keep the backlog manageable.

   Thanks for your understanding and contribution!
7. dosubot

   added

   lifecycle/staleDenotes an issue or PR has remained open with no activity and has become staleDenotes an issue or PR has remained open with no activity and has become stale

   on Oct 18, 2025
8. MrSnoozles commented on Oct 24, 2025

   

   MrSnoozles

   on Oct 24, 2025

   More actions

   Would love to have app support for OpenSearch or ElasticSearch as well. Through elastic or operator does not matter for me.
9. dosubot

   removed

   lifecycle/staleDenotes an issue or PR has remained open with no activity and has become staleDenotes an issue or PR has remained open with no activity and has become stale

   on Oct 24, 2025
10. dosubot commented on Oct 24, 2025

    

    dosubotbot

    on Oct 24, 2025 – with DosuBot

    More actions

    George Gaál (@gecube) The user is still interested in having app support for OpenSearch or ElasticSearch, and they are flexible regarding using Elastic or an operator. Could you please assist with this feature request?
11. Andrei Kvapil (kvaps)

    added 4 commits that reference this issue on Jan 6, 2026

    [linstor] Build linstor-server with custom patches (#1726)

    ...

    d2fc6f8

    [linstor] Build linstor-server with custom patches (#1726)

    ...

    66aec06

    [linstor] Build linstor-server with custom patches (#1726)

    ...

    ad056ee

    [linstor] Build linstor-server with custom patches (#1726)

    ...

    a51e207
12. dosubot

    added

    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become staleDenotes an issue or PR has remained open with no activity and has become stale

    on Jan 23, 2026
13. fuad00 commented on Jan 23, 2026

    

    Alekperov Fuad (fuad00)

    on Jan 23, 2026

    More actions

    opensearch-k8s-operator

    will be great to see opensearch as well!
14. dosubot

    removed

    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become staleDenotes an issue or PR has remained open with no activity and has become stale

    on Jan 23, 2026
15. Timofei Larkin (lllamnyp)

    assigned

    Andrei Kvapil (kvaps)

    on Jan 29, 2026
16. Andrei Kvapil (kvaps)

    added a commit that references this issue on Apr 9, 2026

    linstor: update piraeus-server to v1.33.2 with selected backports (#2331

    ...

    02ed1e0
17. dosubot commented on Apr 30, 2026

    

    dosubotbot

    on Apr 30, 2026 – with DosuBot

    More actions

    Hi, Matthieu ROBIN (@matthieu-robin). I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.

    Issue Summary:

    • You requested support for deploying Elasticsearch, preferably Elastic's operator, with options for single node or cluster and optional TLS.
    • The maintainer asked for clarification on the preferred operator, and you confirmed Elastic's operator.
    • Other users expressed interest in OpenSearch or Elasticsearch, showing some flexibility on the operator choice.
    • The issue remains open but has not progressed recently.
    • I previously requested confirmation on whether this feature is still desired.

    Next Steps:

    • Please let us know if this issue is still relevant to the latest version of Cozy by commenting here.
    • If we do not hear back within 7 days, this issue will be automatically closed.

    Thank you for your understanding and contribution!
18. dosubot

    added

    stale

    on Apr 30, 2026
19. github-actions

    added

    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become staleDenotes an issue or PR has remained open with no activity and has become stale

    and removed

    stale

    on May 1, 2026
20. github-actions commented on May 16, 2026

    

    github-actionsbot

    on May 16, 2026 – with GitHub Actions

    More actions

    Closed because no activity followed the lifecycle/stale warning.
    Reopen if the issue is still relevant.
21. github-actions

    added

    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closedDenotes an issue or PR that has aged beyond stale and will be auto-closed

    on May 16, 2026
22. github-actions

    closed this as not plannedon May 16, 2026