Stephan Lo
43cbd69c9c
- Move all existing docs content (concepts, project, solution) to /docs/v1/ - Add legacy banner component to warn users about archived documentation - Create v1 index page with legacy notice and redirect guidance - Implement automatic banner display for all v1 paths - Preserve all original content for reference during migration This enables incremental content migration while maintaining access to original documentation.
1.3 KiB
1.3 KiB
crossplane dawn?
- Monday, March 31, 2025
Issue
Robert worked on the kindserver reconciling.
He got aware that crossplane is able to delete clusters when drift is detected. This mustnt happen for sure in productive clusters.
Even worse, if crossplane did delete the cluster and then set it up again correctly, argocd would be out of sync and had no idea by default how to relate the old and new cluster.
Decisions
- quick solution: crosspllane doesn't delete clusters.
- If it detects drift with a kind cluster, it shall create an alert (like email) but not act in any way
- analyze how crossplane orchestration logic calls 'business logic' to decide what to do.
- In this logic we could decide whether to delete resources like clusters and if so then how. Secondly an 'orchestration' or let's workflow how to correctly set the old state with respect to argocd could be implemented there.
- keep terraform in mind
- we probably will need it in adapters anyway
- if the crossplane design does not fir, or the benefit is too small, or we definetly ahve more ressources in developing terraform, the we could completley switch
- focus on EDP domain and application logic
- for the momen (in MVP1) we need to focus on EDP higher level functionality