mirror of https://github.com/crossplane/docs.git
Address vale warnings and errors
These weren't introduced by this PR - I think they were missed in recent ones. Signed-off-by: Nic Cope <nicc@rk0n.org>
This commit is contained in:
parent
dc1c242c5f
commit
c005bb353b
|
@ -784,15 +784,15 @@ Function response caching is an alpha feature. Enable it by setting the
|
|||
|
||||
Crossplane can cache function responses to improve performance by reducing
|
||||
repeated function calls. When enabled, Crossplane caches responses from
|
||||
composition functions that include a Time-To-Live (TTL) value.
|
||||
composition functions that include a time to live (TTL) value.
|
||||
|
||||
The cache works by:
|
||||
- Storing function responses on disk based on a hash of the request
|
||||
- Only caching responses with a non-zero TTL
|
||||
- Only caching responses with a nonzero TTL
|
||||
- Automatically removing expired cache entries
|
||||
- Reusing cached responses for identical requests until they expire
|
||||
|
||||
This feature is particularly useful for functions that:
|
||||
This feature helps functions that:
|
||||
- Perform expensive computations or external API calls
|
||||
- Return stable results for the same inputs
|
||||
- Include appropriate TTL values in their responses
|
||||
|
@ -803,6 +803,6 @@ Control the cache behavior with these Crossplane pod arguments:
|
|||
|
||||
- `--xfn-cache-max-ttl` - Maximum cache duration (default: 24 hours)
|
||||
|
||||
The cache stores files in the `/cache/xfn/` directory within the Crossplane pod.
|
||||
The cache stores files in the `/cache/xfn/` directory in the Crossplane pod.
|
||||
For better performance, consider using an in-memory cache by mounting an
|
||||
emptyDir volume with `medium: Memory`.
|
||||
|
|
|
@ -137,7 +137,7 @@ Kubernetes API server when a composed resource changes. For example, when
|
|||
a provider sets the `Ready` condition to `true`.
|
||||
|
||||
{{<hint "important" >}}
|
||||
Real time compositions are a beta feature. Beta features are enabled by
|
||||
Real time compositions are a beta feature. Crossplane enables beta features by
|
||||
default.
|
||||
{{< /hint >}}
|
||||
|
||||
|
|
|
@ -304,17 +304,17 @@ Function response caching is an alpha feature. Enable it by setting the
|
|||
`--enable-function-response-cache` feature flag.
|
||||
{{< /hint >}}
|
||||
|
||||
Operations can benefit from function response caching to improve performance,
|
||||
especially for operations that:
|
||||
- Call the same functions repeatedly with identical inputs
|
||||
Operations can use function response caching to improve performance
|
||||
for operations that:
|
||||
- Call the same functions often with identical inputs
|
||||
- Use functions that perform expensive computations or external API calls
|
||||
- Run frequently through CronOperation or WatchOperation
|
||||
|
||||
The cache works the same way as for Compositions - function responses with
|
||||
time to live values are cached and reused for identical requests until
|
||||
time to live values cache and reuse identical requests until
|
||||
they expire.
|
||||
|
||||
This is particularly useful for Operations that:
|
||||
Function response caching helps Operations that:
|
||||
- Validate configurations using expensive checks
|
||||
- Query external systems for status information
|
||||
- Perform complex calculations that don't change frequently
|
||||
|
|
|
@ -108,6 +108,7 @@ syscall
|
|||
templated
|
||||
TLS
|
||||
tolerations
|
||||
TTL
|
||||
UI
|
||||
VM
|
||||
walkthrough
|
||||
|
|
Loading…
Reference in New Issue