feat: Add webhook integration guide (Phase 3)#381
Draft
Alan-Cha wants to merge 2 commits into
Draft
Conversation
Add documentation and Kubernetes manifests for webhook integration. This completes Phase 3 of the Vault pattern implementation. Provides: - Webhook integration architecture and design - Example Kubernetes manifests (ConfigMap, Deployment) - Webhook implementation guidance for kagenti-operator - Testing and troubleshooting guides - Migration guide from manual to webhook injection Files added: - vault-fetcher/WEBHOOK_INTEGRATION.md (450+ lines) — Integration guide - vault-fetcher/k8s/configmap-vault-fetcher.yaml — Example ConfigMap - vault-fetcher/k8s/example-deployment.yaml — Manual injection example Next steps (Phase 4): - Add CI/CD pipeline for vault-fetcher image - Create demo scenario - Update root CLAUDE.md files - Integration testing Ref: #vault-pattern Stacked on: #380 Signed-off-by: Alan Cha <Alan.cha1@ibm.com>
Complete documentation and CI/CD integration for Vault pattern. This completes Phase 4 (final phase) of the Vault pattern implementation: - Add vault-fetcher to CI/CD build matrix - Update root CLAUDE.md with vault-fetcher documentation - Create comprehensive stacked PR workflow guide Files modified: - .github/workflows/build.yaml — Add vault-fetcher to build matrix - CLAUDE.md — Document vault-fetcher in container images table Files added: - STACKED_PR_WORKFLOW.md (300+ lines) — Complete guide for stacked PR workflow and cascade rebase process Documentation includes: - Current stack structure - Creating stacked PRs (manual and gh-stack) - Critical rebase process when earlier branches change - Handling conflicts - Merging strategy - Common scenarios and troubleshooting - Best practices This document is essential for maintaining the stacked PR workflow, especially when review feedback requires changes to earlier branches. Ref: #vault-pattern Stacked on: PR #TBD (Phase 3) Signed-off-by: Alan Cha <Alan.cha1@ibm.com>
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Phase 3 of the Vault pattern: Webhook integration documentation and Kubernetes manifests.
Stacked on: #380 (Phase 2 - vault-fetcher CLI)
This PR provides complete documentation for integrating vault-fetcher with the kagenti-operator webhook.
What This Adds
Documentation
Kubernetes Manifests
Key Content
Webhook Injection Logic
Shows how kagenti-operator should inject vault-fetcher:
kagenti.io/vault-fetcher-inject: "true")Configuration Examples
Vault Setup
Complete Vault JWT auth configuration:
Files Added
vault-fetcher/WEBHOOK_INTEGRATION.md(450+ lines)vault-fetcher/k8s/configmap-vault-fetcher.yamlvault-fetcher/k8s/example-deployment.yamlTotal: ~577 lines added
Stacked PR Structure
```
main
└─> #379 (Phase 1: authlib/vault)
└─> #380 (Phase 2: vault-fetcher CLI)
└─> THIS PR (Phase 3: Webhook integration)
```
Next Steps (Phase 4)
Review Notes
This PR is documentation-only, no code changes. Focus review on:
Assisted-By: Claude (Anthropic AI) noreply@anthropic.com