You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has some nice benefits such as obviating the need for #86 as the sidecars will start ahead of the wasmCloud host, and as of v1.30 sidecars are also counted towards pod resource utilization, so there aren't any real downsides to the approach.
The text was updated successfully, but these errors were encountered:
Per the blog post introducing "native" sidecar containers and the sidecar containers documentation, the pattern has reached a state (in this case,
beta
) where we should be able to leverage it if we're running in a relatively new (v1.29, which was released onWednesday, December 13, 2023
) version of Kubernetes.This has some nice benefits such as obviating the need for #86 as the sidecars will start ahead of the wasmCloud host, and as of v1.30 sidecars are also counted towards pod resource utilization, so there aren't any real downsides to the approach.
The text was updated successfully, but these errors were encountered: