kubesphere / kubesphere/ks-devops

Add support to select an artifact when creating an image builder

Open
#136 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
164
Forks
140
PR merge metrics
No merged PRs in 30d

Description

**What's it about?**

Currently, users only can upload a binary file manually even they want to create an image builder against the same file multiple times.

![image](https://user-images.githubusercontent.com/1450685/120953286-393cec00-c77f-11eb-86ee-81afda79b3d1.png)

/area devops
/priority medium

**What's the reason why we need it?**

In the real world, users always have their own artifact server. For example, Nexus, MinIO, [Artifactory](https://jfrog.com/artifactory/), etc. It would be very inconvenient if users need to upload it manually.

So, I propose that the Image Builder allows users to choose an artifact from a server (like I mentioned before). There're a couple of things that we might need to consider:

* integration with Nexus, MinIO, etc.
* auth support
* changes from the front-end side

Please leave your comments below if there's anyone who agrees with me. Or just give me a thumb up.

**Area Suggestion**

/kind feature-request

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are identified. Start by mapping the image-builder creation flow and how artifacts are currently uploaded, then investigate the proposed Nexus, MinIO, and Artifactory integrations and authentication requirements. Done means users can select an existing artifact from a supported server when creating an image builder, including the needed frontend changes.

Written by the indexing model from the issue text.

Assessment

Domain
devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.