Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Automatically generate Service Binding metadata? #544

Open
metacosm opened this issue Sep 16, 2021 · 4 comments
Open

Automatically generate Service Binding metadata? #544

metacosm opened this issue Sep 16, 2021 · 4 comments
Assignees
@iocanel
Labels
feature kind/feature Categorizes issue or PR as related to a new feature. needs-discussion Issue needs to be discussed more before working on it

Comments

@metacosm
Copy link
Collaborator

metacosm commented Sep 16, 2021 •
edited by iocanel
Loading

It would make sense to automatically provide metadata so that services created by SDK-created operators are more easily bindable: https://github.com/k8s-service-bindings/spec
@jmrodri jmrodri added kind/feature Categorizes issue or PR as related to a new feature. feature labels Sep 16, 2021
@jmrodri
Copy link
Member

jmrodri commented Sep 16, 2021

This issue is a tracker, needs more information.

@jmrodri jmrodri added the needs-discussion Issue needs to be discussed more before working on it label Sep 16, 2021
@metacosm
Copy link
Collaborator Author

Some feedback from @iocanel to help Service Binding consumers:

  1. produce resources with owner references (it can be helpful to correlate CR with binding secrets)
  2. populate statuses that have explicit references to the binding secret / configmap names (again it can be used for correlation)
  3. Make use of the Service Binding annotations (which may or may not be placeable on the CRD itself).

@iocanel
Copy link
Collaborator

iocanel commented Oct 15, 2021

I will pick this up.

@iocanel
Copy link
Collaborator

iocanel commented Oct 15, 2021

@metacosm @csviri: can you please assign it to me, or grant me karma to do it myself?

@snowdrop-bot snowdrop-bot mentioned this issue Oct 15, 2021
Open
@iocanel iocanel changed the title Automatically generate Service Binding metadata? OPEN Automatically generate Service Binding metadata? Feb 17, 2022
@iocanel iocanel changed the title OPEN Automatically generate Service Binding metadata? OPEN OPEN Automatically generate Service Binding metadata? Feb 17, 2022
@iocanel iocanel changed the title OPEN OPEN Automatically generate Service Binding metadata? Automatically generate Service Binding metadata? Feb 17, 2022
@iocanel iocanel changed the title Automatically generate Service Binding metadata? OPEN Automatically generate Service Binding metadata? Feb 17, 2022
@iocanel iocanel changed the title OPEN Automatically generate Service Binding metadata? Automatically generate Service Binding metadata? Feb 17, 2022
@iocanel iocanel changed the title Automatically generate Service Binding metadata? OPEN Automatically generate Service Binding metadata? Feb 17, 2022
@iocanel iocanel changed the title OPEN Automatically generate Service Binding metadata? OPEN OPEN Automatically generate Service Binding metadata? Feb 17, 2022
@iocanel iocanel changed the title OPEN OPEN Automatically generate Service Binding metadata? OPEN OPEN OPEN Automatically generate Service Binding metadata? Feb 17, 2022
@iocanel iocanel changed the title OPEN OPEN OPEN Automatically generate Service Binding metadata? OPEN OPEN OPEN OPEN Automatically generate Service Binding metadata? Feb 17, 2022
@iocanel iocanel changed the title OPEN OPEN OPEN OPEN Automatically generate Service Binding metadata? Automatically generate Service Binding metadata? Feb 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iocanel iocanel

Labels
feature kind/feature Categorizes issue or PR as related to a new feature. needs-discussion Issue needs to be discussed more before working on it
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jmrodri @metacosm @iocanel