-
Notifications
You must be signed in to change notification settings - Fork 64
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
Implement changes to sync registry operator and registry helm chart - Part 1 #1274
Comments
Cannot be refined and sized until the conclusion of #1193. |
This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days. |
#1193 is the Spike investigation for this issue |
/kind epic Due to scope of the findings in #1193 this issue will be converted into an epic and acceptance criteria broken down into different child issues. |
Final issue has been resolved #1441, closing this epic now.. |
/kind user-story
/kind epic
Which area this user story is related to?
/area registry
User Story
As a registry admin, I want the deployment methods to be synced, so that I can choose my method of devfile registry deployment with out worrying about differences in my deployments.
The setup for the devfile registry helm chart and devfile registry operator are currently inconsistent. We need to ensure that the registry helm chart and registry operator setups are in sync before we can provide official releases.
After investigating what sync changes we need #1193, we need to implement them to meet this objective.
Acceptance Criteria
memoryLimit
field underDevfileRegistry
CRD #1428DevfileRegistry
CRD field for setting the ingress class #1434DevfileRegistry
registry operator CRD #1439The text was updated successfully, but these errors were encountered: