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
If resources are low in the cluster, it may take longer than the max of 30s for the Cluster Admission Controller to receive the responses from the Ziti Webhook. Best practise is to respond as soon as possible and the request throttling is not a good option either, let alone best practise. We most likely need to create a garbage collection to compare the identities that are created in the cluster to the ones on the ziti network and the webhook is probably not the place to do that either, then we may need to do that part of the operator. To me that sounds like the best place for it.
The text was updated successfully, but these errors were encountered:
If resources are low in the cluster, it may take longer than the max of 30s for the Cluster Admission Controller to receive the responses from the Ziti Webhook. Best practise is to respond as soon as possible and the request throttling is not a good option either, let alone best practise. We most likely need to create a garbage collection to compare the identities that are created in the cluster to the ones on the ziti network and the webhook is probably not the place to do that either, then we may need to do that part of the operator. To me that sounds like the best place for it.
The text was updated successfully, but these errors were encountered: