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

Service-Catalog does not refresh authorization data from a secret #2641

Closed
piotrmiskiewicz opened this issue Feb 7, 2019 · 1 comment
Closed

Service-Catalog does not refresh authorization data from a secret #2641

piotrmiskiewicz opened this issue Feb 7, 2019 · 1 comment
Labels
area/service-management Issues or PRs related to service management kind/bug Categorizes issue or PR as related to a bug.

Comments

@piotrmiskiewicz
Copy link
Member

piotrmiskiewicz commented Feb 7, 2019 •
edited
Loading

Description

The broker controller in the Service-Catalog does not refresh sedcret with authorization data (for example basic auth). This may cause an error, when the secret with credentials is changing, for example in GCP broker

Expected result

Service Catalog refreshes authorization data when it is changed

Actual result

Service Catalog does not refresh authorization data from time.

Steps to reproduce

Install service broker with basic auth stored in a secret. Provide wrong credentials, then update the secret with valid credentials. Service Catalog still cannot fetch the catalog.

Related: kubernetes-retired/service-catalog#2563
@piotrmiskiewicz piotrmiskiewicz added kind/bug Categorizes issue or PR as related to a bug. area/service-management Issues or PRs related to service management labels Feb 7, 2019
@piotrmiskiewicz piotrmiskiewicz added this to the Sprint_Gopher_11 milestone Feb 7, 2019
@PK85 PK85 modified the milestones: Sprint_Gopher_11, Backlog_Gopher Feb 7, 2019
@PK85 PK85 modified the milestones: Backlog_Gopher, Sprint_Gopher_13 Mar 15, 2019
@PK85
Copy link
Contributor

PK85 commented Mar 15, 2019

Issue has been fixed.

@PK85 PK85 closed this as completed Mar 15, 2019
grischperl pushed a commit to grischperl/kyma that referenced this issue Nov 10, 2020
Add preset for gardener logs (kyma-project#2641)
aff9455
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/service-management Issues or PRs related to service management kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@PK85 @piotrmiskiewicz