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

Replace Service Catalog references store #2836

Closed
mszostok opened this issue Feb 22, 2019 · 4 comments
Closed

Replace Service Catalog references store #2836

mszostok opened this issue Feb 22, 2019 · 4 comments
Assignees
Labels
area/service-management Issues or PRs related to service management

Comments

@mszostok
Copy link
Contributor

Description

Service Catalog api-server provides the generic subresources on your CR. Service Catalog is using that to store the references.

Unfortunately, this is not supported in CRDs, see CRD docs.

NOTE: It looks like only the ServiceInstance is using that. Here is PR which introduced that.

Solution:

  1. Replace sub-resource operation with patch. See POC implementation.

Concerns:

  • check if this approach is acceptable, cause it's not replacing whole sub-resource functionality, e.g. the RBAC

AC:

  • new approach for storing references is implemented and accepted by Service Catalog team
@mszostok mszostok added the area/service-management Issues or PRs related to service management label Feb 22, 2019
@mszostok mszostok added this to the Sprint_Gopher_12 milestone Feb 22, 2019
@PK85 PK85 modified the milestones: Sprint_Gopher_12, Sprint_Gopher_13 Mar 4, 2019
@mszostok
Copy link
Contributor Author

problem with the solution from POC is that on Update function u can change the references fields.

Maybe we can drop the UpdateReferences func and use only the Update function?

@mszostok mszostok self-assigned this Mar 19, 2019
@mszostok
Copy link
Contributor Author

Remember about DoD:

  • execute make verify and it MUST end without error
  • execute make test-unit and it MUST end without error
  • execute make format
  • check if your changes need to be applied also for svcat. If yes then modify it and then test it also manually. HINT: Create a binary:
    make svcat
    
    generated binary will be placed in bin/svcat/svcat
  • finally, always generate a new image and update tag in chart
  • finally, test service catalog by installing chart and walkthrough happy path flow both for namespace-scope and cluster-wide brokers. Happy path means creating and deleting all objects.

@PK85 PK85 modified the milestones: Sprint_Gopher_13, Sprint_Gopher_14 Mar 25, 2019
@mszostok
Copy link
Contributor Author

@PK85 PK85 modified the milestones: Sprint_Gopher_14, Sprint_Gopher_15 Apr 8, 2019
@mszostok
Copy link
Contributor Author

waiting for kyma-incubator/service-catalog#17 to be merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/service-management Issues or PRs related to service management
Projects
None yet
Development

No branches or pull requests

2 participants