sync to refactored break - #2
Open
brownzebra wants to merge 2374 commits into
Open
Conversation
EAI-6099 Parametrize Minio & Postgresql usernames and OpenBAO domain in Helm
…-overview dashboard
This commit selectively reverts parts of PR #692 (EAI-5893) that added support for multiple helm value files. Changes: - Removed valuesFiles support from single-source app definitions in cluster-apps.yaml - Modified bootstrap.sh render_actual_helm_manifests() to use valuesFile (singular) instead of valuesFiles - Reverted SBOM validation script to pre-EAI-5893 version - Removed sources/kaiwo/values.yaml Kept unchanged: - root/values.yaml (kaiwo OCI configuration - newer functionality depends on this) - sbom/components.yaml (current kaiwo metadata is correct) - sbom/generate-compare-components.sh (already updated for OCI support in commit 089da0c) - OCI multi-source support in cluster-apps.yaml (valuesFiles retained for OCI functionality) - bootstrap.sh render_actual_helm_manifests() function (modified to remove valuesFiles, kept the function) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
OCI-based apps like kaiwo use repoURL instead of path. The validation script needs to check for app existence (not just non-null path) and normalize empty/null values for proper comparison. This fixes the CI failure where kaiwo showed as: cluster-configs='' vs components.yaml='null'
Replace the chart field with path for OCI repositories in ArgoCD Application specs, aligning with modern ArgoCD OCI support. Defaults to "." when path is not explicitly defined. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Partially revert EAI-5893: Remove valuesFiles from single-source apps
merge main into grafana-user-and-httproute
Grafana user and httproute, keeping old dashboards, premade kubernetes dashboards, initial cluster health dashboard
get grafana into v210 branch
Revert "get grafana into v210 branch"
going to recreate from main after merge so as to not break existing envs pointing to this branch; some -rc refs still need cleaning, so this is not basis for official v2.2.0
chore: remove -rc refs to prepare for v2.2.0 release
fix: ignore skipBackgroundRequests for kyverno policy for aiwb
- update first deployment installed apps - boostrap.sh is not present any more so update accordingly
docs: update main readme
…-step Add more detailed way to verify objects were mirrored from minio to seaweedfs
* feat: custom port for https pod * parameterize remaining port 443 in envoy-gateway-config * parameterize port 443 with single gateway port config
…rgoproj.io/sync-options: SkipDryRunOnMissingResource=true (clean retry over hard error)
…boostrap-script fix: remove deprecated script from release-pipeline
…tion fix via feature: add retry policy to cluster-apps.yaml template
Details to deploy on OpenShift environment
Provision a write credential for AIWB's ADR-0002 Scenario 2 key store, scoped to secrets/apikeys/* instead of reusing the root token: - secret-manager (reconciling, every 5m + init) idempotently ensures apikeys-write-policy and mints a scoped token at secrets/aiwb-openbao-token, re-minting only when the stored one is missing or invalid. No renewal machinery (nothing else in the stack renews); the token carries the default TTL and rotates on expiry. - aiwb-external-secrets: an ExternalSecret materializes that token into the aiwb namespace as aiwb-openbao-token, which the AIWB backend already consumes as OPENBAO_TOKEN. ESO reads it via the existing readonly store. Policy capabilities match the AIWB client exactly: data create/read/update and metadata create/update/delete (delete_version_after + revocation). The OCI publish of aiwb-external-secrets and the root repoVersion bump are handled by the external release pipeline, not here.
docs: update 2.2.0 refs to 2.2.2 in migration from 2.1.x guide
…edential EAI-7277: scoped OpenBao write credential for the API-key KV path
Add option to use local Helm values for apps
Minor correction
* feat: overhaul LGTM stack v1.0.8 with official Grafana image * lgtm overhaul v4 * old PROMETHEUS_EXTRA_ARGS to single line so retention.size flag isn't dropped * expose collector memory_limiter settings via values.yaml * docs: add otel-lgtm-stack per-cluster tuning guide * docs: polishing the doc
* Upgrade seaweedfs operator to 0.1.29 * Disable seaweed ingress, as we create HTTPRoutes. Remove seaweed crds (part of operator now) * Replace init-job with seaweedfs native bucket yaml definition * fix wrong values object reference * Add missing config to root values * Add missing value from root values * Fix scoping error in the bucket template * Upgrade to latest (0.1.36) * fix wrong value for Versioning attribute * Fix windows end line issue * Add quotation marks to get helm to correctly read value as string * Change the backwards-compatibility-enabling service "filer-s3" (the naming is anathema to the latest seaweed operator) to point to the new seaweedfs s3 service * Keep the httproute unchanged, no unneeded changes should be added * add a dummy file in crds, to allow migrating without removing seaweedfs-crds from apps * Update SBOM * update sbom components.yaml
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
15 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.
No description provided.