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
Currently, Stowaway enters the ready state almost immediately, as there is no readiness probe implemented at all. Yet, the Operator depends on this state in order to perform activities, such as retrieving the peer secrets and storing them in Kubernetes secrets. There is a race condition: Kubernetes declares the Stowaway Pod ready, but the peer secrets are not yet generated. This leads to errors in the Operator log.
Why is this no big deal at the moment? - since the Operator retries to extract the peer's secret, it is going to work at some point. However, this can be easily improved by introducing a meaningful readiness probe for the Stowaway Pod.
Why would such a feature be important to you?
Prevent error logs in the Gefyra Operator from showing up. They are misleading and unnecessary.
Anything else we need to know?
The Stowaway Kubernetes Deployment is created here:
If that file exists: wonderful, Stowaway is ready and Operator can extract the file.
If Stowaway is still booting up, this file does not yet exist and Stowaway would not be ready. In this case, Operator will wait some time longer.
What is the new feature about?
Currently, Stowaway enters the
ready
state almost immediately, as there is no readiness probe implemented at all. Yet, the Operator depends on this state in order to perform activities, such as retrieving the peer secrets and storing them in Kubernetes secrets. There is a race condition: Kubernetes declares the Stowaway Pod ready, but the peer secrets are not yet generated. This leads to errors in the Operator log.Why is this no big deal at the moment? - since the Operator retries to extract the peer's secret, it is going to work at some point. However, this can be easily improved by introducing a meaningful readiness probe for the Stowaway Pod.
Why would such a feature be important to you?
Prevent error logs in the Gefyra Operator from showing up. They are misleading and unnecessary.
Anything else we need to know?
The Stowaway Kubernetes Deployment is created here:
gefyra/operator/gefyra/resources/deployments.py
Lines 16 to 92 in 81d5583
We could implement a readiness probe like so:
If that file exists: wonderful, Stowaway is ready and Operator can extract the file.
If Stowaway is still booting up, this file does not yet exist and Stowaway would not be ready. In this case, Operator will wait some time longer.
gefyra/operator/gefyra/stowaway.py
Lines 17 to 57 in 81d5583
The text was updated successfully, but these errors were encountered: