-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: CFServiceInstance
and CFServiceBinding
resources should implement the ProvisionedService
duck type
#549
Labels
Comments
gnovv
added a commit
that referenced
this issue
Feb 3, 2022
- Added status conditions field to service bindings - WIP Completed happy-path integration tests Co-authored-by: Andrew Costa <[email protected]> Co-authored-by: Akira Wong <[email protected]>
julian-hj
added a commit
that referenced
this issue
Feb 8, 2022
update CFServiceInstance and CFServiceBinding [finishes #549]
julian-hj
added a commit
that referenced
this issue
Feb 8, 2022
- cfservicebinding_controller_test and cfserviceinstance_controller_test had variables not getting re-initialized between test runs, causing flakiness. #549 Co-authored-by: Julian Hjortshoj <[email protected]>
julian-hj
added a commit
that referenced
this issue
Feb 8, 2022
- cfservicebinding_controller_test and cfserviceinstance_controller_test had variables not getting re-initialized between test runs, causing flakiness. #549 Co-authored-by: Julian Hjortshoj <[email protected]>
davewalter
added a commit
that referenced
this issue
Feb 8, 2022
Fix cross test contamination in controller units
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Blockers/Dependencies
No response
Background
As an App Developer
I want the
CFServiceInstance
andCFServiceBinding
resources to implement theProvisionedService
duck type from the K8s Service Binding specificationSo that they can interoperate with other K8s Service Binding aware projects (such as Kpack)
Acceptance Criteria
CFServiceInstance
Secret Exists
GIVEN I have applied a
CFServiceInstance
CR and the correspondingSecret
existsWHEN I
kubectl -n SPACE_GUID get cfserviceinstance CF_SERVICE_INSTANCE_NAME
THEN I see that
status.binding.name
on theCFServiceInstance
is set to the name of theSecret
AND I see a
BindingSecretAvailable
condition instatus.conditions
indicating that the secret is availableSecret Does Not Exist
GIVEN I have applied a
CFServiceInstance
CR that hasstatus.binding.name
set on itWHEN I delete the referenced
Secret
THEN I see that
status.binding.name
on theCFServiceInstance
is removedAND I see a
BindingSecretAvailable
condition instatus.conditions
indicating that the secret does not existCFServiceBinding
Secret Exists
GIVEN I have applied a
CFServiceBinding
CR and the correspondingSecret
existsWHEN I
kubectl -n SPACE_GUID get cfservicebinding CF_SERVICE_BINDING_NAME
THEN I see that
status.binding.name
on theCFServiceBinding
is set to the name of theSecret
AND I see a
BindingSecretAvailable
condition instatus.conditions
indicating that the secret is availableSecret Does Not Exist
GIVEN I have applied a
CFServiceBinding
CR that hasstatus.binding.name
set on itWHEN I delete the referenced
Secret
THEN I see that
status.binding.name
on theCFServiceBinding
is removedAND I see a
BindingSecretAvailable
condition instatus.conditions
indicating that the secret does not existDev Notes
ProvisionedService
duck typeThe text was updated successfully, but these errors were encountered: