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.

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

Implement memoryLimit field under registry operator reconcile #1429

Open
3 tasks
Tracked by #1446
michael-valdron opened this issue Feb 1, 2024 · 5 comments
Open
3 tasks
Tracked by #1446

Implement memoryLimit field under registry operator reconcile #1429

michael-valdron opened this issue Feb 1, 2024 · 5 comments
Assignees
@Horiodino
Labels
area/registry Devfile registry for stacks and infrastructure lifecycle/stale Stale items. These items have not been updated for 90 days.

Comments

@michael-valdron
Copy link
Member

michael-valdron commented Feb 1, 2024 •
edited
Loading

Which area/kind this issue is related to?

/area registry

Issue Description

With the addition of the new memoryLimit field to the DevfileRegistry CRD #1428, changes would need to be done to the reconcile procedure under the controller to have the registry operator update this field when a change in value is applied.

Parent Epic: #1446

Acceptance Criteria

  • Implement update mechanism for memoryLimit field under controller reconcile procedure
  • Update documentation to include memoryLimit usage
  • Run integration tests to verify changes
@openshift-ci openshift-ci bot added the area/registry Devfile registry for stacks and infrastructure label Feb 1, 2024
This was referenced Feb 1, 2024
Closed
Open
@michael-valdron
Copy link
Member Author

Parent issue updated to #1446.

@Jdubrick Jdubrick moved this to Refinement in Devfile Project Feb 29, 2024
@michael-valdron michael-valdron mentioned this issue Mar 4, 2024
Merged
3 tasks
@github-actions GitHub Actions
Copy link

github-actions bot commented May 8, 2024

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.

@github-actions github-actions bot added the lifecycle/stale Stale items. These items have not been updated for 90 days. label May 8, 2024
@Horiodino
Copy link

anyone working on this issue ?

@Horiodino Horiodino mentioned this issue Sep 20, 2024
Open
3 tasks
@github-actions github-actions bot removed the lifecycle/stale Stale items. These items have not been updated for 90 days. label Sep 27, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Jan 2, 2025

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 120 days.

@github-actions github-actions bot added the lifecycle/stale Stale items. These items have not been updated for 90 days. label Jan 2, 2025
@michael-valdron michael-valdron removed the lifecycle/stale Stale items. These items have not been updated for 90 days. label Jan 2, 2025
@github-actions GitHub Actions
Copy link

github-actions bot commented Apr 3, 2025

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 120 days.

@github-actions github-actions bot added the lifecycle/stale Stale items. These items have not been updated for 90 days. label Apr 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Horiodino Horiodino

Labels
area/registry Devfile registry for stacks and infrastructure lifecycle/stale Stale items. These items have not been updated for 90 days.
Projects
Devfile Project
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@michael-valdron @Horiodino