Skip to content

Canonical MaaS as an Image Provider #1688

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
vasartori opened this issue Feb 17, 2025 · 1 comment · May be fixed by #1695
Open

Canonical MaaS as an Image Provider #1688

vasartori opened this issue Feb 17, 2025 · 1 comment · May be fixed by #1695
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@vasartori
Copy link
Contributor

Feature Request: MaaS as an Image Provider

Is your feature request related to a problem? Please describe.

No, this is a new feature request.

Describe the solution you'd like

It would be beneficial to add MaaS (Metal as a Service) as a supported image provider in image-builder.

MaaS is a platform that allows bare-metal servers to be managed like cloud instances, making it a valuable addition for provisioning and deployment workflows.

Describe alternatives you've considered

An alternative is using the QEMU provider to generate images for MaaS, but this approach is suboptimal since MaaS has dedicated methods for image generation that could be better integrated into image-builder.

Additional context

Supporting MaaS natively would enable better integration for users who rely on it for managing bare-metal infrastructure, aligning with the goal of making image-builder a versatile tool for various environments.

I can work on this feature request. Please let me know if there are any guidelines or existing discussions I should follow before getting started.

/kind feature
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 17, 2025
@vasartori vasartori linked a pull request Feb 25, 2025 that will close this issue
Open
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for Canonical MaaS Provider vasartori/image-builder
3 participants
@vasartori @k8s-ci-robot @k8s-triage-robot