Skip to content

Conversation

@Aryan-sharma11
Copy link
Member

Purpose of PR?:

Fixes #

Does this PR introduce a breaking change?

If the changes in this PR are manually verified, list down the scenarios covered::

Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs

Checklist:

  • Bug fix. Fixes #
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • PR Title follows the convention of <type>(<scope>): <subject>
  • Commit has unit tests
  • Commit has integration tests

@Aryan-sharma11 Aryan-sharma11 force-pushed the fix-imagepullsecrets branch 3 times, most recently from 07f5a3d to 2cf149a Compare December 17, 2025 10:34
@Aryan-sharma11 Aryan-sharma11 force-pushed the fix-imagepullsecrets branch 3 times, most recently from 9ef6631 to 20c5797 Compare December 19, 2025 17:38
@rksharma95
Copy link
Collaborator

just to note, we'll need to update kubearmor-client as well right!

@Aryan-sharma11 Aryan-sharma11 force-pushed the fix-imagepullsecrets branch 4 times, most recently from f0d5022 to f2ee5c4 Compare December 22, 2025 10:58
Signed-off-by: Aryan-sharma11 <[email protected]>
@rksharma95 rksharma95 merged commit dd8fe49 into kubearmor:main Dec 23, 2025
15 of 16 checks passed
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.

3 participants