AFAIK continuously welded tracks (like those used in high speed rail) are also slightly tensioned, so a break in a single point could make it look like a whole section of track is missing, as tension is released.
CWT is laid in such a way that it has net zero stress in a "neutral" temperature, which naturally depends on the climate. Both extreme heat and extreme cold can cause damage, buckling and fracturing/embrittlement respectively, and choosing the neutral temperature is balancing act. But even if completely cut, track cannot shrink longitudinally much at all, it's the job of the sleepers and the ballast to keep it anchored in place. And if the track is laid on a concrete slab rather than ballast, it isn't moving anywhere.
Fun fact: the reason modern concrete or composite sleepers (e.g. [1]) have a slightly concave profile is to better resist lateral forces (i.e. buckling) than traditional straight-profile wooden sleepers.
Standard text patches (diffs) are great because they work with all text files but for a specific representation like JSON you can do a lot better. In terms of code volume it's a lot lighter to find a node based on a json path than applying a diff.
There are multiple reasons and limitations with current tooling that we want to overcome.
We have abstracted all packages as custom resources and have a controller that reconciles these resources to (1) enable drift detection. Additionally, we use admission controllers (2) to validate dependencies and package configurations before they are applied to the cluster, while also working with custom resources to store and update the status of installed packages.
Genuinely interested. What problems did you have dealing with the standard reconciliation mechanism provided by ArgoCD and by k8s itself. I understand the advantage of the operator approach, but it might be hard to show the state in ArgoCD and somewhat breaks the idea of gitops.
Can we benefit your project in a more limited but agentless way? Limiting the types and CRDs we allow in k8s makes operations better, especially with the aggressive upgrade cycle that k8s already imposes.
A deeper integration into Argo CD (similar as how helm is integrated) will be needed to in order to display all status conditions.
I don't think that idea of gitops is broken if the glasskube package controller and all custom resources are versioned you will always lead to a reproducible result.
> Can we benefit your project in a more limited but agentless way?
We are building a central package repository with a lot of ci / cd testing infrastrucutre to increase quality of kubernetes packages in general: https://github.com/glasskube/packages
This is a problem for me as a language learner on mobile. I set a keyboard with (for example) Russian, and suddenly the world looks Russian, even though I am far from comfortable in it yet. I wish there were a way for the browser to ignore some system languages. This is worse for apps because I also get served with localised versions, where I need to uninstall, remove system language and re-install.
Deep down in the sun photons are absorbed almost as soon as they are created. In a sense the photons at the surface of the sun are the result of nuclear reactions thousands of years back. However neutrinos escape pretty fast and so can be used to gauge the status of nuclear reactions now.
reply