[Feature]: Missing addon support like CNI, apps from managed clusters

[dipankardas011]

✨ Feature Name

Addon support in controller.Metadata

🎯 Purpose

It will help users to specify what CNI or addon which EKS and other provide

📝 Feature Description

for now we can only represent the CNI plugins as addon and other addons we can think of managing not through the controller.Metadata{} but via a different addons controller which can integrate with EKS, AKS, ... thus aggregating the addons into a single plane and also our own addons like kcm 🤔

🎁 Benefits

support to pick and choose which CNI to install

⚖️ Potential Drawbacks

• we need to rethink about how the addon management across self-managed and managed cluster can work!!

🔄 Alternatives Considered

No response

🎯 Impact Areas

• 🖥️ CLI - Command line interface
• 🎨 UI - User interface
• 📚 Documentation
• ⚙️ Core Features
• 🔌 External Integrations
• 🧪 Testing Infrastructure

🛠️ Implementation Details

• possibility of depricating Apps method from cloud interface and have a 2 seperate:
  • CNI() only works when provisioning the cluster ( we can utilize the already developed ksctl/ksctl/v2/pkg/addons)
  • Addons() which can validate and also install the addon based on the usr input. ( we can utilize the already developed ksctl/ksctl/v2/pkg/addons)

📋 Agreements

• 🤝 I agree to follow the Contribution Guidelines
• 🔍 I have searched for similar feature requests
• 💬 I will participate in the discussion about this feature

[dipankardas011]

When the thing returns the CLusterAddons make sure the versions are also present if we are installing from ksctl like cilium and flannel version so that we are transparent about them before creating them

[dipankardas011]

When the thing returns the CLusterAddons make sure the versions are also present if we are installing from ksctl like cilium and flannel version so that we are transparent about them before creating them

We can ignore this for now. Because cilium and flannel versions fall under Config *string and which is custom and we should not populate just for version but should be available for all ksctl cni configs, also making the available versions to the clients will need to have a external interface method for returning the versions specific to the application.