Frank Farzan
Frank Farzan
A weakness of [execution configuration pattern] is that it interleaves configuration and code. For example, gatekeeper constraint templates wrap Rego code in KRM. Similarly, starlark code is wrapped in StarlarkRun...
Following changes are needed to adhere to [Functions Spec v1]: - [x] Migrate internal annotations: - [x] `config.k8s.io/id` -> `internal.config.kubernetes.io/id` - [x] `config.kubernetes.io/path` -> `internal.config.kubernetes.io/path` - [x] `config.kubernetes.io/index` -> `internal.config.kubernetes.io/index`...
We have a stop-gap overview page: https://kpt.dev/?id=overview The end state should have a high production value. For comparison, see these landing pages: https://www.terraform.io/ https://kustomize.io/ https://www.pulumi.com/
Currently, there is no notion of built-in functions. The first-party function images in `gcr.io/kpt-fn` have no special meaning or treatment and are released and versioned independently from the kpt CLI....
### Bug Description When using `livekit-agents[google] v1.2.18` with Gemini Live API (2.5), if a user sends text input while the model is generating a response, it successfully interrupts the model...
This includes examples in the book and in the reference docs.
We're going to automatically enforce a style guide on all documentation (reference, book, catalog). This will be a growing list of rules, starting with: - [x] All references to the...
``` $ cd /tmp/hello-world-workspace $ kpt pkg diff diff /var/folders/yw/dmxc0tlx7td3n1mjpwlq21yr0048dv/T/kpt-941888986/deploy.yaml /var/folders/yw/dmxc0tlx7td3n1mjpwlq21yr0048dv/T/kpt-571299697/deploy.yaml 21c21 < app: hello1 --- > app: hello ```
A problem that function developers run into: Emitting a debug log message to stdout. Because stdout is used for machine-to-machine protocol [1], it leads to cryptic failures from `kpt fn`....
Both of these should work: https://kpt.dev/book/ https://kpt.dev/book Latter gives a 404 now.