Azure / Azure/AKS

[Feature] AKS Fleet Manager | To Orchestrate, Coordinate or Manage AKS Backup Services

Open
#4,169 3 comments 1 reaction 1 assignee Claimed by @sjwaight View on GitHub
feature-request fleet-manager
Dominant language
TypeScript
Stars
2.1k
Forks
395
Avg merge
2d 22h
Merged PRs (30d)
13

Description

### Is your feature request related to a problem? Please describe.
No, I could not find an existing issue or bug that would relate to this feature request.

### Describe the solution you'd like
As an AKS (Azure Kubernetes Service) administrator managing multiple clusters within a fleet, I often encounter challenges in orchestrating and managing backup services across these clusters efficiently. To address this, I propose the integration of AKS Fleet Manager with AKS backup services, enabling centralized management and coordination of backups for all clusters within the fleet.

### Describe alternatives you've considered

**Alternative 1: Leveraging AKS Fleet Manager to Install AKS Backup Extension**

One alternative involves utilizing AKS Fleet Manager to install the AKS Backup extension across all clusters within the fleet. This approach capitalizes on Fleet Manager's ability to orchestrate and unify resource objects and services across its members. However, it remains uncertain whether Fleet Manager can orchestrate AKS policies or extensions seamlessly. This uncertainty raises the possibility of requiring a separate feature request to enable Fleet Manager's capability to orchestrate AKS policies or extensions effectively.

**Pros:**
1. **Centralized Management:** AKS Fleet Manager provides a centralized platform for managing AKS clusters, potentially simplifying the deployment and management of backup extensions.
2. **Unified Configuration:** By leveraging Fleet Manager, administrators can ensure consistent backup configurations across the entire AKS fleet, reducing the likelihood of configuration discrepancies.
3. **Integration Potential:** If AKS Fleet Manager can orchestrate AKS policies or extensions in the future, this approach could offer a comprehensive solution for managing both cluster configurations and backup services.

**Cons:**
1. **Uncertain Capability:** The current uncertainty regarding AKS Fleet Manager's ability to orchestrate AKS policies or extensions introduces ambiguity and may require additional investigation or a separate feature request.
2. **Dependency on Future Updates:** Achieving the desired functionality may depend on future updates or enhancements to AKS Fleet Manager, potentially leading to delays in implementation.
3. **Complexity:** If the integration requires significant changes to AKS Fleet Manager's architecture or capabilities, it could introduce complexity and increase the development effort required for implementation.

**Alternative 2: Using Infrastructure as Code (IaC) Options like Terraform**

A defacto alternative to use involves utilizing Infrastructure as Code (IaC) tools like Terraform to manage AKS backups. While not as convenient as using AKS Fleet Manager, Terraform would offer a solution for automating infrastructure provisioning and management, including backup configurations.

**Pros:**
1. **Flexibility:** Terraform provides flexibility in defining backup configurations as code, allowing administrators to tailor backup policies to meet specific requirements.
2. **Version Control:** Infrastructure configurations managed with Terraform can be version-controlled, enabling better tracking of changes and facilitating collaboration among team members.
3. **Multi-Cloud Support:** Terraform supports multi-cloud environments, allowing organizations to manage backups consistently across different cloud providers if needed. However, it would be compelling if AKS Fleet Manager could manage GCP's GKE or AWS's EKS.

**Cons:**
1. **Manual Management:** Unlike AKS Fleet Manager, Terraform requires manual configuration and management of backup policies, potentially increasing administrative overhead.
2. **Learning Curve:** Adopting Terraform may require additional time and resources to familiarize team members with its syntax and best practices, especially if they are not already experienced with IaC tools.
3. **Potential Complexity:** Depending on the complexity of the backup configurations and the size of the AKS fleet, managing backups with Terraform could become complex and difficult to maintain over time.

### Additional context
Not at this time

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.