Giji first build #1390
Open
Giji first build #1390
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
Contributor
YustinaKvr
commented
Sep 3, 2025
YustinaKvr
commented
- Kustomization files
- 3 cronjobs
* Initial commit with dumped and adapted values file for ArgoCD * temp commit * Self-managed ArgoCD by ArgoCD App in app * Creation of ArgoCD app in app - dumped and addapted ArgoCD values file, including best security practices - re-organized folder structure to use local & upstream helm charts - migrated and modified upstream helm charts correspondingly to the folder structure - introduced ArgoCD's applicationSets for the usage of two or more applications together - additional of argocd clusters as a sealed secrets manifests - added configManagementPlugin * Templating all kustomize apps - added manifests for argocd projects, applications, applicationsSets - added manifests for kustomize applicationSet, which includes all applications within kustomize folder - added `app-config.yaml` to each kustomize apps to define target namespace, argocd project, syncPolicy and server destination - removed root-of-app-of-apps - ToDo: missing swift-proxy-swiss kustomize app * Updating Argocd values files based on ansible playbook manifest and removing argocd plugins templates * feat: add preprod cluster support for ArgoCD and monitoring stack - Add preprod cluster to ArgoCD ApplicationSets for argocd, cert-manager, prometheus, and victoria-metrics - Add preprod cluster support for grafana, victoria-metrics-auth, promtail, and cert-exporter applications - Create preprod configuration files for all monitoring components: - ArgoCD with OIDC integration and vault plugin support - Grafana with Keycloak authentication and datasource configs - Prometheus stack with alerting and ingress configuration - Victoria Metrics cluster and auth components - Promtail for log forwarding to Loki - Fix prometheus additional manifests to use cluster-specific values - Remove commented out application configurations to clean up codebase * Fixing helm templating * Re-using vault plugin template * Addition of vault upstream helm chart * Adapted ArgoCD values file for intengration with vault * Updating cert-manager * Removing leftovers from value-preprod.yaml of argocd * Creating templates and values file for argocd clusters * fixing up cert-manager additional manifests * Testing commit * Testing templating of cluser-secrets * Fixing up templating of cluster secrets * ANother fix of cluster secrets template * Amother try * And another fix * Another try * working example * test * test * test * test * test * Fixed template of cluster secret * Partial preprod readiness: - adapted multiple configs to desired use cases - cleanup of unnecessary files/fodlers - restructuralization - upgraded version of cert-manager * Addition of adapted aplictionSet manifests and appliations values file * Adding argocd unpacked helm chart * Testing out another solution with seperated chart section * Changing argocd application template * Reverting changes * Addition of argocd-additional-manifest values file and helm templates * WiP: Partial values files of applications and applicationSets * adapting the applciation template for kustomize usage * Removing unnecessary data form kustomize subfolders and using first kustomize app in argocd applications * Changing eco to eco-preprod endpoints * Addition of preprod cluster * Fix of the cluster template * Fixing up clusters template and renaming the argocd templates * Test * Final fix if cluster templating * Renaming some templates * Moving out repositories manifest and creating separated values file * Changes after rebase
* Enabling openapi-validator * Removing netpol * Addition of argocd-vault-kustomize plugin * fixing up role bindings * fixin up openapi validator * fixin up rolebindings * Watching working branch in some of the the applications * updating version of openapi-validator * updating version of openapi-validator * moving to 0.3.1 * adding reportportal references --------- Co-authored-by: Vladimir Hasko <[email protected]>
* Enabling secret reference in stead of configmap with plain text * Fixing up clusterissuers * Updating the rbac roles of Argocd * Fixing up rbac roles in argocd * Removing not necessary manifests
* Update openapi validator to 0.3.2 * Update to 0.3.2
YustinaKvr
requested review from
otcbot,
vladimirhasko,
tischrei and
LukasCuperDT
as code owners
LukasCuperDT
changed the base branch from
main
to
Helm_charts_restructure&Pre-Prod_setup
LukasCuperDT
force-pushed
the
giji_first_build
branch
from
c76b171 to
419124f
Compare
* Update openapi to 0.3.3 * Update to 0.3.3
* Init commit * Finalisation of outline helm chart - addition of outline argocd app updated with parameters - adapted values file to use values from parameters - prefinal version ready * Fixing up parametrizastion in plugin * Stable values-preprod file of upstream's Argocd * Fixing indentations * another fix of k patcher * Excluding patch of the secret if it exists * rolling back kubectl patcher * Fixing up outline * Fixing up otuline pvc * Fix helm template validation errors for Outline - Add minimal Redis configuration to satisfy chart template requirements - Set Redis host to 'redis-disabled' to prevent connection attempts - Use dummy Redis password for template validation - This resolves the 'Redis password is required' template error * Fix nginx ingress pathType for ACME challenges - Change pathType from ImplementationSpecific to Prefix - This resolves ACME challenge validation errors with nginx admission webhook - Error: 'path /.well-known/acme-challenge/... cannot be used with pathType Exact' * Update Redis configuration to use minimal instance * Addition of local helm chart for outline
LukasCuperDT
force-pushed
the
giji_first_build
branch
3 times, most recently
from
67cd4a1 to
c9905a3
Compare
️✅ There are no secrets present in this pull request anymore.If these secrets were true positive and are still valid, we highly recommend you to revoke them. 🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request. |
LukasCuperDT
force-pushed
the
giji_first_build
branch
from
a0e071a to
1e7b0c8
Compare
LukasCuperDT
force-pushed
the
Helm_charts_restructure&Pre-Prod_setup
branch
6 times, most recently
from
5d13bd9 to
2770532
Compare
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.