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
Now that the servicebinding controller holds two secrets - one for each binding format (vcap_services and servicebinding.io) it is weird to set only one of these secrets as the .status.binding duck type. According to the servicebinding.io spec it is possible to project a secret directly to a workload instead of depending on a duck type.
Action to take
Project servicebinding.io bindings directly from the servicebinding.io binding secret
The text was updated successfully, but these errors were encountered:
This change is not really worth it as the direct secret projection still needs a binding status field. Whether it is a duck type or not is not too important.
Background
Now that the servicebinding controller holds two secrets - one for each binding format (vcap_services and servicebinding.io) it is weird to set only one of these secrets as the
.status.binding
duck type. According to the servicebinding.io spec it is possible to project a secret directly to a workload instead of depending on a duck type.Action to take
Project servicebinding.io bindings directly from the servicebinding.io binding secret
The text was updated successfully, but these errors were encountered: