Steven E. Harris
Steven E. Harris
As we watch for progress with the aforementioned KEP, this issue remains relevant.
As before, this issue remains relevant.
This looks it would touch two TypeScript files, the YAML schema for the Action, the documentation, and a unit test. Is anyone else considering implementing this soon?
More proposals for this new load restriction mode's name: - _Root Only Shallowly_ - _Root Shallowly_ - _Root Start_ - _Root Referenced_
Bazel removed its `--experimental_use_sandboxfs` command-line flag in commit bazelbuild/bazel@b6e2693f83a7ece37c902416de26a3807b541ceb, such that it's no longer viable to use _sandboxfs_ to work around the "Root Only" load restrictor's intolerance for symbolic links...
/remove-lifecycle stale
Your _DaemonSet_ is lacking the "app" label mentioned in your patch's label selector. You have that label in the _DaemonSet_'s pod spec template, but not on the _DaemonSet_ itself.
I had the same—or at least a similar—need recently: A vendor changed the schema used in their _CRD_, effectively renaming two fields ([in Kong's _IP Restriction_ plugin](https://docs.konghq.com/hub/kong-inc/ip-restriction/#parameters), per Kong/kong#8560, "config.blacklist"...
Perhaps the Webhook program could accept a posture-conveying command-line flag that could switch it out of its current wary, distrustful mode and activate other modes, such as "unsafe" or "supervised,"...
As [stated earlier](https://github.com/Kong/kong/issues/10654#issue-1662813630), I'm using Kong proxy version 3.2.2 and ingress controller version 2.9.2. Here's another manifest: KongPlugin manifest ```yaml apiVersion: configuration.konghq.com/v1 kind: KongPlugin metadata: name: opentelemetry-to-collector namespace: default plugin:...