chaloem
My feedback
66 results found
-
17 votes
chaloem supported this idea ·
-
17 votes
ARM support is now in progress for the Community Operator (https://github.com/mongodb/mongodb-kubernetes-operator) and will be released in the next few weeks.
ARM support for the Enterprise Operator is TBD but is in the roadmap, likely for 2024.
chaloem supported this idea ·
-
18 votes
chaloem supported this idea ·
-
18 votes
chaloem supported this idea ·
-
18 votes
chaloem supported this idea ·
-
20 votes
chaloem supported this idea ·
-
20 votes
chaloem supported this idea ·
-
22 votes
chaloem supported this idea ·
-
23 votes
chaloem supported this idea ·
-
33 votes
Hi All,
We are developing a solution directly in Ops Manager that will support swapping their S3 snapshot storage without terminating the backup. Ops Manager will allow you to update the S3 snapshot store ID in the backup job document and the next scheduled snapshot will be a full snapshot in the new S3 snapshot store after the update. This is specifically for S3 stores only at this time.
We are targeting this feature to be included in a minor release of Ops Manager 8 by mid 2025 at this time.
I will update this feedback item once launched.
chaloem supported this idea ·
-
24 votes
chaloem supported this idea ·
-
52 votes
chaloem supported this idea ·
-
45 votes
chaloem supported this idea ·
-
47 votes
chaloem supported this idea ·
-
8 votes
chaloem supported this idea ·
-
45 votes
We’re currently researching the best way to add support for this.
chaloem supported this idea ·
-
6 votes
chaloem supported this idea ·
-
7 votes
We're planning an investigation into this in Q2 (May-July for us). It's something more than one customer has asked for and allowing an Atlas ID to be used rather than a reference for another K8s resource feels like a reasonable approach.
No commitments for now till we've investigated in a little more detail.
chaloem supported this idea ·
-
8 votes
This is something we're considering for the future.
But the biggest problem we need to solve is that it's incredibly easy to create/delete/update databases within a deployment via many other interfaces. But if this happens, the Operator's source of truth (the custom resources) won't contain the changes, and the Operator would overwrite the changes using it's source of truth.
chaloem supported this idea ·
-
4 votes
chaloem supported this idea ·