Init of preprod branch #1458
Draft
Init of preprod branch #1458
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
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 23016484 | Triggered | Generic Database Assignment | 85fa909 | kubernetes/helm_charts/upstream/outline/values-preprod.yaml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 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
preprod
branch
2 times, most recently
from
846c7c2 to
dc717ad
Compare
…cutor storage class
- Removed nodeSelector: dedicated=zuul-ci from all 8 base component files - Deleted remove-node-selectors.yaml patch (no longer needed) - Updated kustomization.yaml to remove patch reference - Allows pods to schedule on any available nodes
- Add patch to change zuul-config PVC from csi-nas to csi-sfsturbo - csi-nas was failing with provisioning errors - Deleted old zuul-var-zuul-executor-0 PVC (will be recreated with correct storageClassName)
LukasCuperDT
force-pushed
the
preprod
branch
2 times, most recently
from
b1956d0 to
becabb8
Compare
- csi-sfsturbo requires special parameters (everest.io/volume-as) - Use nfs-rw flex-volume based storage class instead
- Pods expect exact secret names without hash suffixes - Added disableNameSuffixHash: true to both secret generators
- Changed container names from component-specific (zuul-scheduler, zuul-web, etc) to 'zuul' - Base components use 'name: zuul' for all containers - Patches were creating new containers instead of patching existing ones - This caused volume mounts from base to be lost
* Anubis Preprod * Fix issue * test * test * test * test * test * test * Add kustomize for anubis * Remove Helm chart for anubis * Remove Helm chart for anubis * Switch ingress overwrite to anubis folder * switch branch
- Update tenant configuration to use single zuul-infra instead of three separate repos - Remove zuul-config, otc-zuul-jobs, zuul-project-config references - Add opentelekomcloud-infra/zuul-infra as sole config-project - Simplify nodepool to Debian-only configuration - Remove debian-bullseye, pod-default, pod-fedora-latest, ubuntu-jammy labels - Keep only debian (VM) and pod-debian (Kubernetes pod) labels - Use Debian Bookworm exclusively - Update ZUUL_CONFIG_REPO environment variable to point to zuul-infra - Align with zuul-infra repository structure and Debian-only strategy
- dependencytrack-api: 2000m -> 10m CPU (actual: 1m) - dependencytrack-frontend: 1000m -> 10m CPU (actual: 1m) - circle-partner-navigator cpn-backend: 500m -> 10m CPU (actual: 1m) Total CPU savings: ~4980m (~5 CPUs) to enable node scheduling
This reverts commit 28b86f3.
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.