Skip to content

feat: make peer-pods policy Azure-specific#17

Closed
butler54 wants to merge 2 commits into
validatedpatterns:mainfrom
butler54:feat/conditional-peerpods-policy
Closed

feat: make peer-pods policy Azure-specific#17
butler54 wants to merge 2 commits into
validatedpatterns:mainfrom
butler54:feat/conditional-peerpods-policy

Conversation

@butler54
Copy link
Copy Markdown
Contributor

@butler54 butler54 commented Jun 1, 2026

Summary

Make the peer-pods ConfigMap policy conditional on Azure platform. This prevents rendering peer-pods configuration on bare metal clusters where it's not applicable.

Changes

  • Wrap templates/peer-pods-cm.yaml with {{- if eq .Values.global.clusterPlatform "Azure" }} guard
  • Bump Chart.yaml version to 0.2.0 (minor feature release)

Testing

  • Deploy on Azure cluster: peer-pods policy renders and enforces ConfigMap
  • Deploy on bare metal: peer-pods policy does not render

Resolves Wave 1 PR 1E from attestation hardening plan.

Co-Authored-By: Claude Sonnet 4.5 noreply@anthropic.com

butler54 added 2 commits May 27, 2026 12:46
Make the peer-pods ConfigMap policy conditional on Azure platform to avoid
rendering on bare metal clusters where peer-pods are not used.

Changes:
- Wrap templates/peer-pods-cm.yaml with {{- if eq .Values.global.clusterPlatform "Azure" }}
- Bump Chart.yaml version from 0.1.0 to 0.2.0 (minor bump for new feature)

hub-to-spoke-initdata-policy.yaml remains platform-independent.
Signed-off-by: Chris Butler <chris.butler@redhat.com>
@butler54
Copy link
Copy Markdown
Contributor Author

butler54 commented Jun 1, 2026

Closing as duplicate. This work was already merged via #16 and released as v0.2.0.

@butler54 butler54 closed this Jun 1, 2026
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.

1 participant