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
Sometimes SpinKube users may prefer to skip using the Spin Operator and choose to define their own K8s deployments, for example if using Argo Rollout resources. We should document how the Shim expects information such as OTEL parameters, etc to be passed inside PodSpecs (usually as Container environment variables) to make it easier for users to construct their own deployments.
The text was updated successfully, but these errors were encountered:
Sometimes SpinKube users may prefer to skip using the Spin Operator and choose to define their own K8s deployments, for example if using Argo Rollout resources. We should document how the Shim expects information such as OTEL parameters, etc to be passed inside PodSpecs (usually as Container environment variables) to make it easier for users to construct their own deployments.
The text was updated successfully, but these errors were encountered: