forked from silogen/cluster-forge
-
Notifications
You must be signed in to change notification settings - Fork 0
sync to refactored break #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
brownzebra
wants to merge
1,495
commits into
brownzebra:clean-working-directory
Choose a base branch
from
silogen:main
base: clean-working-directory
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
Fix typo at components.yaml
fix: missing kueue values
…older Fix missing commits from input folder
fix: valid yaml file for chrony-node-exporter.yaml
SBOM integration to release pipeline
Bump release 1 0 2
feat: kaiwo v0.2.0-rc5
feat: git commit automation for a new release changes
fix: git commit before release creation
fix: typo
fix: keep both archives in sync
… 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)
chore: remove values_ha.yaml as required by CI
Eai 936 t shirts cleaning PR checks
fix: pipe all the valuesObject key-value paris
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.
No description provided.