Skip to content
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.

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

[FEATURE] Only one instance of ShipwrightBuild kind should be allowed on a given cluster #153

Open
1 task done
jkhelil opened this issue Oct 23, 2023 · 1 comment · May be fixed by #150
Open
1 task done

[FEATURE] Only one instance of ShipwrightBuild kind should be allowed on a given cluster #153

jkhelil opened this issue Oct 23, 2023 · 1 comment · May be fixed by #150
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Milestone

Comments

@jkhelil
Copy link
Contributor

jkhelil commented Oct 23, 2023

Is there an existing feature request for this?

  • I have searched the existing feature requests

Is your feature request related to a problem or use-case? Please describe.

User can create multiple ShipwrightBuild instance on the same cluster, however ShipwrightBuild controller is watching all builds, buildruns kinds. installing multiple hipwrightBuild instance leads to a multiple encorching controllers

Describe the solution that you would like.

  • ShipwrightBuild has a fixed name example 'shipwright-operator'
  • Validate that only one instance of ShipwrightBuild is allowed by name 'shipwright-operator'

Describe alternatives you have considered.

No response

Anything else?

No response

@jkhelil jkhelil added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 23, 2023
@kevydotvinu kevydotvinu linked a pull request Nov 14, 2023 that will close this issue
4 tasks
@adambkaplan adambkaplan added this to the Backlog milestone Nov 20, 2023
@qu1queee
Copy link

From Refinement, is this work ongoing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

3 participants