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
For transition scenarios where the wicked core components are updated one by one (which will be the case for Kubernetes and alike), the wicked components should do a standard version check on the portal API when calling it. It should pass an "expected version" e.g. as a header to the upstream API, and if present, this version is checked by the API and in case it does not match the call is rejected.
This will be optional behavior which will be implemented by the standard components, but which will not be enforced by the portal API in case the additional header is not present (this will be a similar behavior as described in #36).
Containers which receive such a faulty version, and/or have a version mismatch, will fail early and fast with a descriptive error message.
As soon as the version of the container has been updated, the operations would return to normal again.
The text was updated successfully, but these errors were encountered:
For transition scenarios where the wicked core components are updated one by one (which will be the case for Kubernetes and alike), the wicked components should do a standard version check on the portal API when calling it. It should pass an "expected version" e.g. as a header to the upstream API, and if present, this version is checked by the API and in case it does not match the call is rejected.
This will be optional behavior which will be implemented by the standard components, but which will not be enforced by the portal API in case the additional header is not present (this will be a similar behavior as described in #36).
Containers which receive such a faulty version, and/or have a version mismatch, will fail early and fast with a descriptive error message.
As soon as the version of the container has been updated, the operations would return to normal again.
The text was updated successfully, but these errors were encountered: