Eai 936 t shirts #538
Closed
Eai 936 t shirts #538
Conversation
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
feat: kyverno policy to force PVC on small/med. to be RWO (or RWOP if that was requested); llm: ambitious aditions that will be redacted, but preserving in history as example usage
Remove unnecessary security-baseline placeholder policies that were added as examples but not required for the minimal viable implementation. Update documentation to focus on cluster-size-specific PVC access mode conversion while preserving exact main branch compatibility for large clusters. - Remove security-baseline Chart.yaml and disallow-privileged.yaml - Update MODULAR_KYVERNO_DESIGN.md to focus on minimal implementation - Clarify in values files that base policies match main branch exactly - Ensure large clusters receive zero additional policies beyond main branch
Add missing valuesObject support to cluster-apps.yaml template to enable inline values configuration alongside existing valuesFile and helmParameters. This resolves deployment issues for applications using valuesObject in app-dev customizations. Also update Chart.yaml with descriptive metadata including proper title, keywords, maintainers, and improved description explaining the ClusterForge Application Root purpose. Fixes deployment compatibility for inline configuration patterns used in app-dev customizations.
… and Gitea The bootstrap script expects values_cf.yaml files for core services but these were missing, causing bootstrap failures. Created these files by copying from the existing default values files: - sources/argocd/values_cf.yaml (from values_ha.yaml for HA config) - sources/openbao/values_cf.yaml (from values.yaml) - sources/gitea/values_cf.yaml (from values.yaml) Fixes bootstrap script path resolution and enables successful cluster deployment.
…ive values.yaml Remove nested values_cf.yaml files and align with main branch structure: - Remove sources/*/values_cf.yaml files (incorrect nested approach) - Update root/values.yaml to use valuesObject for core components (ArgoCD, Gitea, OpenBao, cert-manager) - Update bootstrap script to use native chart values.yaml with --set overrides - Maintain separation: root files contain overrides, component charts use native values This aligns with main branch pattern where root values contain all customizations and component directories only contain native chart files.
- Alpha-sort enabledApps in base values.yaml for easier cross-comparison - Add missing common apps to base (cilium, grafana, longhorn, prometheus, otel-config) - Remove massive duplication from values_small.yaml (reduced from 47 to 1 enabledApp override) - Remove massive duplication from values_medium.yaml (reduced from 46 to 1 enabledApp override) - Follow proper inheritance: size files only override differences from base - Small/Medium only add: kyverno-policies-storage-local-path - Large inherits all base apps (no enabledApps duplication) - Eliminated 64+ lines of redundant enabledApps declarations Values structure now follows DRY principle with clear inheritance hierarchy.
The RBAC policy 'g, argocd-users, role:admin' contains commas which were being misinterpreted by Helm's --set parser as parameter separators. Escaped commas as 'g\, argocd-users\, role:admin' to fix parsing. Resolves: failed parsing --set data: key 'argocd-users' has no value
Move all root-level documentation files to /docs folder with consistent lowercase and underscore naming convention for better organization: - CLUSTER_SIZE_CONFIGURATION.md → docs/cluster_size_configuration.md - KYVERNO_ACCESS_MODE_POLICY.md → docs/kyverno_access_mode_policy.md - MODULAR_KYVERNO_DESIGN.md → docs/kyverno_modular_design.md - scripts/bootstrap.md → docs/bootstrap_guide.md - docs/secrets-management-architecture.md → docs/secrets_management_architecture.md This creates a centralized documentation structure following standard naming conventions and improves discoverability.
Create comprehensive documentation for ClusterForge's dual repository GitOps pattern and values inheritance system: - External vs Local deployment modes (values.yaml vs values_cf.yaml) - Size-specific inheritance hierarchy with DRY principles - Multi-source ArgoCD configuration for repository separation - Developer workflow for local cluster configuration management - Bootstrap transition pattern from external to autonomous operation This documents the sophisticated GitOps architecture that enables clusters to transition from external dependency to local autonomy while maintaining declarative configuration management.
Major updates to Product Requirements Document reflecting recent architectural improvements: - Add dual repository GitOps pattern documentation - Document size-aware configuration with DRY inheritance - Update component layers with new additions (Cilium, Longhorn, etc.) - Add Kyverno modular policy system documentation - Include comprehensive documentation structure references - Add new functional requirements for size-aware deployment - Document air-gap and local development capabilities This brings the PRD up to date with the current sophisticated architecture supporting external/local deployment modes and streamlined cluster size configurations.
Major update to main README reflecting recent architectural improvements: - Add size-aware deployment examples (small/medium/large clusters) - Document dual repository GitOps architecture - Reorganize components by logical layers with updated descriptions - Add comprehensive documentation table linking to /docs folder - Include cluster sizing and values inheritance information - Update component descriptions to reflect current architecture - Add clear navigation to specialized documentation This provides a comprehensive overview of ClusterForge capabilities and guides users to detailed documentation for specific topics.
…t exist properly)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
post-checks-update