Skip to content

Fix Kyverno require-valid-owner-reference for Neo4j operations pods on 5.26#540

Open
riggi-alekaj wants to merge 10 commits into
5.26from
rigert/add-pod-onwer-reference-5-26
Open

Fix Kyverno require-valid-owner-reference for Neo4j operations pods on 5.26#540
riggi-alekaj wants to merge 10 commits into
5.26from
rigert/add-pod-onwer-reference-5-26

Conversation

@riggi-alekaj
Copy link
Copy Markdown
Collaborator

  • Convert operations workload from standalone Pod to Job so created Pods have ownerReferences
  • Introduce dedicated operations ServiceAccount with least-privilege RBAC (get on auth secret only)
  • Add securityContext, resource limits, and configurable imagePullPolicy

@riggi-alekaj riggi-alekaj requested a review from bfeshti as a code owner April 27, 2026 11:57
@riggi-alekaj riggi-alekaj changed the title Rigert/add pod onwer reference 5 26 Fix Kyverno require-valid-owner-reference for Neo4j operations pods on 5.26 Apr 27, 2026
@riggi-alekaj riggi-alekaj force-pushed the rigert/add-pod-onwer-reference-5-26 branch from 17f7e26 to 81f01ea Compare April 29, 2026 07:41
@riggi-alekaj riggi-alekaj force-pushed the rigert/add-pod-onwer-reference-5-26 branch from 81f01ea to 688650d Compare April 29, 2026 09:55
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.

2 participants