When using Claude Code, it's possible to opt out of having one's sessions be used for training. But is that opt out for everything? Or only message content, such that there could remain sufficient metadata to derive…
It's called 'setting an example'. One might disagree with value of the example being set, but I'm not sure I would characterize his choices as in any way convenient for him.
I used kinesis advantage for 15 years, switched to a glove80 for the past 2, but recently went back to kinesis with an advantage2. The glove80 is very nice, but my hands are big enough that the kinesis thumb cluster…
Even in the best case of what you are describing, how are these tools configured and their configuration maintained except via PRs to the repos in question? For every such change, N PRs having to be proposed, reviewed…
Have you heard of OpenShift 4? Self-hosted Kubernetes by Red Hat. Every little piece of the control plane is its own 'operator' (basically a microservice) and every operator is developed in its own repo. A github search…
If you like grainy mustard, I can’t recommend Kozliks’ Triple Crunch enough: https://www.kozliks.com/
The number of deployed CRDs is not likely to be an issue. The number and size of custom resources (CRs - instances of CRDs) is potentially an issue. Scalability is relative, and depends on many factors including but not…
Not sure why you’re being downvoted. OpenAPI schema generation is one of the most challenging elements of developing with CRDs. Anyone who is not an apimachinery SME is likely to struggle at some point to get their…
tl;dr If you’re operating with CRDs at trivial scale, you probably having nothing to worry about. But operating with CRDs at scale is a different story and suggests careful testing with the specific applications…
When using Claude Code, it's possible to opt out of having one's sessions be used for training. But is that opt out for everything? Or only message content, such that there could remain sufficient metadata to derive…
It's called 'setting an example'. One might disagree with value of the example being set, but I'm not sure I would characterize his choices as in any way convenient for him.
I used kinesis advantage for 15 years, switched to a glove80 for the past 2, but recently went back to kinesis with an advantage2. The glove80 is very nice, but my hands are big enough that the kinesis thumb cluster…
Even in the best case of what you are describing, how are these tools configured and their configuration maintained except via PRs to the repos in question? For every such change, N PRs having to be proposed, reviewed…
Have you heard of OpenShift 4? Self-hosted Kubernetes by Red Hat. Every little piece of the control plane is its own 'operator' (basically a microservice) and every operator is developed in its own repo. A github search…
If you like grainy mustard, I can’t recommend Kozliks’ Triple Crunch enough: https://www.kozliks.com/
The number of deployed CRDs is not likely to be an issue. The number and size of custom resources (CRs - instances of CRDs) is potentially an issue. Scalability is relative, and depends on many factors including but not…
Not sure why you’re being downvoted. OpenAPI schema generation is one of the most challenging elements of developing with CRDs. Anyone who is not an apimachinery SME is likely to struggle at some point to get their…
tl;dr If you’re operating with CRDs at trivial scale, you probably having nothing to worry about. But operating with CRDs at scale is a different story and suggests careful testing with the specific applications…