braghettos

E se il mio sistema acquaponico stesse dando i suoi frutti? What if my aquaponic system is working, and working really well? @Docker @IBMWatson @ArrowGlobal @ArrowEurope @Raspberry_Pi @TheMagPi

@fatih @PlanetScale github.com/krateoplatform… is the second approach based on Helm values.schema.json and github.com/krateoplatform… is based on Swagger v3 (OpenAPI)

@fatih @PlanetScale Hi Fatih! In Krateo PlatformOps we took two approaches: we have implemented a runtime that adds the ability to pause the reconciliation loop, disable the create or delete phase, forces to write events on conditions change. The other approach is to automatically generate

Is there any open source k8s operator/controller that is idiomatic written, and you would adopt the patterns in your company? I’m working for years on operators at scale. We have a solid foundation and frameworks at @PlanetScale to run thousands of databases on Kubernetes with high availability. It’s battle tested. But I wonder what else people are using. For example I tried out kro, but found it immature for our use case yet (it’s a cool idea though). I like how you can pass down parent references to child object, and bubble up child statuses at the parent. I also like the dependency rules. But it’s very abstract and we need more low level primitives.

@fatih @PlanetScale github.com/krateoplatform… is the first approach

@fatih @PlanetScale these controllers starting from a Helm values.schema.json or a OpenAPIv3 schema

@ibuildthecloud Try buildjet

This is how crappy github free runners are (or how awesome @depotdev is). I started a build on github. Then realized I should try using depot instead. I signed up, configured depot, made the one line change in my workflow, push it and the new build finished before the original.

Best. Tweet. EVER.

Today, we were at @Microsoft House in #Milan to showcase a preview of the new #Composable #Operations. Stay tuned for the official launch of V2 🚀

Problem: #helm is not natively integrated into #kubernetes. There's no validation of values during the installation phase of a chart and no reconciliation when a resource is manually changed or deleted. Solution: @krateoplatform - give it a try! killercoda.com/krateoplatform…

He's really #growingwithcloudnative @CloudNativeFdn

Who's next? Welcome to @braghettos and @foogaro (🥳🥳🥳) who will explore how to use caching mechanisms to improve Kubernetes API server performance and how to use events to invalidate the cache efficiently. Sounds interesting, right? Then join us! @KubernetesDays #kcditaly

@paw_lean Derbyshire and surroundings are simply amazing

@braghettos Yes!

Factory reset 🪬

@infracloudio @krateoplatform 😉

________ is to Kubernetes, what spinach is to Popeye. Tell us in the comments👇 (Wrong answers only)

@leodido my therapist told me it's not normal to have recurring dreams about syntax errors and parsers, then I wake up and I realize I was sleeping on the sofa of my therapist that told me which is ..

my therapist told me it's not normal to have recurring dreams about syntax errors and parsers, I disagree

@rejektsio @ThSchue Great @ThSchue !

Happy to have @ThSchue present the new Keptn Lifecycle Toolkit at #Rejekts2023 in Amsterdam!🚴 Thomas will show how the toolkit can help you with additional insights into the deployment process! 🎫s👉eventbrite.com/e/465064138357

@mmikulicic @ibuildthecloud @AlexJonesax 2/2 So if a CR must be used, then a definition for that CR that validates the schema must be implemented via CRD (or APIService if using an aggregation layer). I would avoid the x-kubernetes-preserve-unknown-fields option, since it invalidates the structural OpenAPI v3 validation

@mmikulicic @ibuildthecloud @AlexJonesax 1/2 The first issue is about the presence of a jsonschema in the package (Helm chart doesn't require to have one, we are generating it automatically if it doesn't exist). The second issue is about the possibility to override default values, which must be expressed via CR specs.

An Operator is a synthesis of human behaviour, codified into software to facilitate the full lifecycle management of an application.

@mmikulicic @ibuildthecloud @AlexJonesax 2/2 In this way, if my CR of that generated CRD is correctly applied, all the specs have been validated and are aligned with the helm chart values. We are working on this approach to better integrate Helm charts as first-class citizens in Kubernetes.

@mmikulicic @ibuildthecloud @AlexJonesax 1/2 What if we don't have a generic CR but a well-defined CRD generated automatically from a helm chart values.yaml file or values.json.schema file? Having a generic CR doesn't validate specs that can be potentially non-aligned with the values of the helm chart.

ICYMI: Yesterday I posted the second installment in the @kubernetesio API Server Adventures series. This one is all about watching and caching, including looking at how watch caches relieve pressure on @etcdio. danielmangum.com/posts/k8s-asa-…