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 we are validating the chane of credential type of service instance in the api shim. This works well for API users, but not for direct kubectl users. If a kubectl user changes the credential type in the secret of the service instance the sevice binding reconciler would keep re-trying infinitely with a backoff each time getting an immutable secret type error.
Action to take
Ensure that the service binding controller sets Ready condition to True/False depending on the outcome. In the example above we should set Ready to false if we get an immutable secret type error.
The api shim should wait for the binding to reach Ready=true or fail after some timeout period.
The text was updated successfully, but these errors were encountered:
Background
Currently we are validating the chane of credential type of service instance in the api shim. This works well for API users, but not for direct kubectl users. If a kubectl user changes the credential type in the secret of the service instance the sevice binding reconciler would keep re-trying infinitely with a backoff each time getting an immutable secret type error.
Action to take
The text was updated successfully, but these errors were encountered: