Average Ratings 0 Ratings
Average Ratings 0 Ratings
Description
As the utilization of Kubernetes continues to increase, organizations are discovering the necessity of managing and deploying several clusters in order to support essential capabilities such as geo-redundancy, scalability, and fault isolation for their applications. Submariner enables your applications and services to operate seamlessly across various cloud providers, data centers, and geographical regions. To initiate this process, the Broker must be set up on a singular Kubernetes cluster. It is essential that the API server of this cluster is accessible to all other Kubernetes clusters that are linked through Submariner. This can either be a dedicated cluster or one of the already connected clusters. Once Submariner is installed on a cluster equipped with the appropriate credentials for the Broker, it facilitates the exchange of Cluster and Endpoint objects between clusters through mechanisms such as push, pull, and watching, thereby establishing connections and routes to other clusters. It's crucial that the worker node IP addresses on all connected clusters reside outside of the Pod and Service CIDR ranges. By ensuring these configurations, teams can maximize the benefits of multi-cluster setups.
Description
Failover Clustering in Windows Server (and Azure Local) allows a collection of independent servers to collaborate, enhancing both availability and scalability for clustered roles, which were previously referred to as clustered applications and services. These interconnected nodes utilize a combination of hardware and software solutions, ensuring that if one node encounters a failure, another node seamlessly takes over its responsibilities through an automated failover mechanism. Continuous monitoring of clustered roles ensures that if they cease to function properly, they can be restarted or migrated to uphold uninterrupted service. Additionally, this feature includes support for Cluster Shared Volumes (CSVs), which create a cohesive, distributed namespace and enable reliable shared storage access across all nodes, thereby minimizing potential service interruptions. Common applications of Failover Clustering encompass high‑availability file shares, SQL Server instances, and Hyper‑V virtual machines. This functionality is available on Windows Server versions 2016, 2019, 2022, and 2025, as well as within Azure Local environments, making it a versatile choice for organizations looking to enhance their system resilience. By leveraging Failover Clustering, organizations can ensure their critical applications remain available even in the event of hardware failures.
API Access
Has API
Yes
API Access
Has API
No
Integrations
Active Directory
No
Kubernetes
Yes
Microsoft 365
No
Microsoft Azure
No
Microsoft Hyper-V
No
PowerShell
No
SIOS DataKeeper
No
SQL
No
Windows Server
No
Integrations
Active Directory
Yes
Kubernetes
No
Microsoft 365
Yes
Microsoft Azure
Yes
Microsoft Hyper-V
Yes
PowerShell
Yes
SIOS DataKeeper
Yes
SQL
Yes
Windows Server
Yes
Pricing Details
No price information available.
Free Trial
No
Free Version
No
Pricing Details
No price information available.
Free Trial
Yes
Free Version
No
Deployment
Web-Based
Yes
On-Premises
No
iPhone App
No
iPad App
No
Android App
No
Windows
No
Mac
No
Linux
No
Chromebook
No
Deployment
Web-Based
Yes
On-Premises
No
iPhone App
No
iPad App
No
Android App
No
Windows
No
Mac
No
Linux
No
Chromebook
No
Customer Support
Business Hours
No
Live Rep (24/7)
No
Online Support
Yes
Customer Support
Business Hours
Yes
Live Rep (24/7)
No
Online Support
Yes
Types of Training
Training Docs
Yes
Webinars
No
Live Training (Online)
No
In Person
No
Types of Training
Training Docs
Yes
Webinars
Yes
Live Training (Online)
Yes
In Person
Yes
Vendor Details
Company Name
Submariner
Website
submariner.io
Vendor Details
Company Name
Microsoft
Founded
1975
Country
United States
Website
learn.microsoft.com/en-us/windows-server/failover-clustering/failover-clustering-overview