Skip to content

Conversation

@kyledong-suse
Copy link
Collaborator

What this PR does / why we need it:

  1. Store WP status inside agent
  2. Expose the WP status through GRPC
  3. If the WP deployment failed, rollback the WP
  4. Add check to avoid overwriting existing policies

Which issue(s) this PR fixes

fixes #174

Special notes for your reviewer:

Checklist:

  • squashed commits into logical changes
  • includes documentation
  • adds unit tests
  • adds or updates e2e tests

@kyledong-suse kyledong-suse changed the title [WIP]feat: store workload policy status in agent feat: store workload policy status in agent Feb 10, 2026
@github-project-automation github-project-automation bot moved this to Pending Review in Runtime Enforcer Feb 10, 2026
@kyledong-suse kyledong-suse marked this pull request as ready for review February 10, 2026 19:52
Copy link
Collaborator

@holyspectral holyspectral left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like much more than just storing the policy status in agent! It generally looks good to me. I think some improvement can be done as to how we deal with rollback.

Copy link
Collaborator

@holyspectral holyspectral left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. The only nit is that the last commit shouldn't be a chore. lol Other than that it looks great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[time-boxed] store workload policy status inside our agent

3 participants