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
Since on Triton, Pod containers will never (At least that's my understanding) share a namespace, so Pods will only ever have 1 long running container associated with them. this isn't Normal K8S behavior so it should be well documented for the Consumer.
I don't plan on supporting or implementing sizing an instance via "Resources" and will just use a label via Package.
etc.
The text was updated successfully, but these errors were encountered:
Document Triton Differences.
Examples:
Since on Triton, Pod containers will never (At least that's my understanding) share a namespace, so Pods will only ever have 1 long running container associated with them. this isn't Normal K8S behavior so it should be well documented for the Consumer.
I don't plan on supporting or implementing sizing an instance via "Resources" and will just use a label via Package.
etc.
The text was updated successfully, but these errors were encountered: