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.

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

start using SBO again #5221

Closed
4 tasks
kadel opened this issue Nov 10, 2021 · 6 comments
Closed
4 tasks

start using SBO again #5221

kadel opened this issue Nov 10, 2021 · 6 comments
Assignees
Labels
area/binding Issues or PRs related to `odo add/delete binding *` commands or Service Binding Operator priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).

Comments

@kadel
Copy link
Member

kadel commented Nov 10, 2021

new SBO version hard codes binding definitions for some of the operators. This might make using SBO with odo much easier

  • investigate if we can leverage this to fix odo link flow broken on latest SBO 0.10. #5084
  • Investigate which Operators' annotations have been hard-coded by SBO and add tests for these in odo
    • Doesn't have to be all operators in a single sprint.
    • MVP would be to manually test it, but automate at least one in the first sprint

/triage needs-information

@openshift-ci openshift-ci bot added the triage/needs-information Indicates an issue needs more information in order to work on it. label Nov 10, 2021
@kadel
Copy link
Member Author

kadel commented Nov 10, 2021

/assign
/kind service-binding

@openshift-ci
Copy link

openshift-ci bot commented Nov 10, 2021

@kadel: The label(s) kind/service-binding cannot be applied, because the repository doesn't have them.

In response to this:

/assign
/kind service-binding

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kadel
Copy link
Member Author

kadel commented Nov 24, 2021

/priority high
due to #5207

@openshift-ci openshift-ci bot added the priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). label Nov 24, 2021
@kadel kadel removed their assignment Nov 24, 2021
@dharmit dharmit removed this from For Consideration in Sprint 211 Nov 29, 2021
@dharmit dharmit added this to For Consideration in Sprint 211 via automation Dec 2, 2021
@dharmit
Copy link
Member

dharmit commented Dec 2, 2021

For sprint 211, let's figure out how to move back to using SBO again. The code to be uncommented is at:

// IsServiceBindingSupported checks if resource of type service binding request present on the cluster
func (c *Client) IsServiceBindingSupported() (bool, error) {
// Detection of SBO has been removed from issue https://github.com/redhat-developer/odo/issues/5084
return false, nil
// return c.IsResourceSupported("binding.operators.coreos.com", "v1alpha1", "servicebindings")
}

Uncomment and test things.

@dharmit dharmit self-assigned this Dec 2, 2021
@dharmit dharmit moved this from For Consideration to To Do in Sprint 211 Dec 2, 2021
@feloy feloy added this to For Consideration in Sprint 212 via automation Dec 16, 2021
@dharmit dharmit mentioned this issue Dec 27, 2021
4 tasks
@joshira-rh joshira-rh removed this from For Consideration in Sprint 212 Jan 10, 2022
@joshira-rh joshira-rh added this to For Consideration in Sprint 213 via automation Jan 10, 2022
@joshira-rh joshira-rh assigned feloy and unassigned dharmit Jan 10, 2022
@feloy
Copy link
Contributor

feloy commented Jan 10, 2022

The service binding operator v1.0 is setting default annotations to the Redis operator CRD, which are using non mandatory fields, and that causes problems with odo integration tests not using these fields (specifically .spec.redisSecret on redis.redis.opstreelabs.in/v1beta1).

redhat-developer/service-binding-operator#1088

@joshira-rh joshira-rh added triage/ready estimated-size/S (5-10) Rough sizing for Epics. Less then one sprint of work for one person and removed triage/needs-information Indicates an issue needs more information in order to work on it. labels Jan 12, 2022
@kadel kadel moved this from For Consideration to In Progress in Sprint 213 Jan 13, 2022
@joshira-rh joshira-rh removed this from In Progress in Sprint 213 Feb 2, 2022
@kadel kadel added area/binding Issues or PRs related to `odo add/delete binding *` commands or Service Binding Operator and removed area/service-binding labels Mar 11, 2022
@kadel kadel removed the estimated-size/S (5-10) Rough sizing for Epics. Less then one sprint of work for one person label Mar 24, 2022
@valaparthvi
Copy link
Contributor

We are using SBO for tests and library when it's not available. I am going to close this issue. If anyone thinks it's still an issue, feel free to reopen it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/binding Issues or PRs related to `odo add/delete binding *` commands or Service Binding Operator priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

5 participants