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

Improve Dangling Resource Cleanup Strategy and Configuration Linting #77

Closed
5 of 10 tasks
Tracked by #125
robertwol opened this issue Jul 18, 2023 · 1 comment
Closed
5 of 10 tasks
Tracked by #125
Assignees
Labels

Comments

@robertwol
Copy link

robertwol commented Jul 18, 2023

User Story

As a developer or system administrator, I want to ensure that the Open Component Model (OCM) project has an effective strategy for cleaning up unwanted custom resources and a linting mechanism to validate configuration files. This will help prevent the accumulation of dangling resources in the live system and provide better clarity on stalled conditions in controllers. By addressing these issues, we can enhance the overall stability and maintainability of the OCM project.

Epic link:

Potential Tasks:

  • 1: Implement a garbage collection mechanism for identifying and removing dangling resources in the live system.
  • 2: Define clear guidelines and documentation for identifying stalled conditions in controllers to avoid ambiguity.
  • 3: Develop a validation framework for configuration files to ensure their correctness and adherence to specified standards.

Acceptance criteria:

Definition of Done:

  • The garbage collection mechanism is implemented, tested, and integrated into the OCM project codebase.
  • Guidelines and documentation for identifying stalled conditions in controllers are documented and shared with the OCM community.
  • The validation framework for configuration files is developed and integrated, providing meaningful error messages for any configuration file issues.
  • Relevant unit tests and integration tests are created and passed successfully.
  • Documentation is updated to include information about the garbage collection mechanism, guidelines for stalled conditions, and the configuration file validation framework.
  • The changes are reviewed and approved by the project maintainers.
  • The improvements are deployed to the production environment or the appropriate staging/testing environment.

Related issues:

@robertwol robertwol transferred this issue from open-component-model/ocm Jul 18, 2023
@morri-son morri-son transferred this issue from open-component-model/ocm-controller Mar 14, 2024
@morri-son morri-son added the component/ocm-controllers OCM Controllers label Mar 17, 2024
@shivenduverma-sap shivenduverma-sap removed their assignment Mar 17, 2024
@morri-son morri-son moved this from 🆕 ToDo to 📋 Next-UP in OCM Backlog Board Apr 29, 2024
@Skarlso Skarlso self-assigned this May 2, 2024
@fabianburth fabianburth moved this from 📋 Next-UP to 🆕 ToDo in OCM Backlog Board May 16, 2024
@Skarlso
Copy link
Contributor

Skarlso commented May 24, 2024

I'm not sure what to do about the garbage collection part. There is not much that we can do. We outsource the deployment to Flux, and set prune. There isn't much else to be done here.

We also have now a configuration validation in place with Schemes and CUE.

@Skarlso Skarlso closed this as completed May 24, 2024
@github-project-automation github-project-automation bot moved this from 🆕 ToDo to 🍺 Done in OCM Backlog Board May 24, 2024
@ocmbot ocmbot bot moved this from 🍺 Done to 🔒Closed in OCM Backlog Board May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🔒Closed
Development

No branches or pull requests

4 participants