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 servicebinding.io duck types with direct secret reference #3103

Closed
georgethebeatle opened this issue Feb 9, 2024 · 1 comment
Closed
Labels

Comments

@georgethebeatle
Copy link
Member

georgethebeatle commented Feb 9, 2024

Background

Now that the servicebinding controller holds two secrets - one for each binding format (vcap_services and servicebinding.io) it is weird to set only one of these secrets as the .status.binding duck type. According to the servicebinding.io spec it is possible to project a secret directly to a workload instead of depending on a duck type.

Action to take

Project servicebinding.io bindings directly from the servicebinding.io binding secret

@georgethebeatle georgethebeatle moved this from 🧊 Icebox to 🇪🇺 To do in Korifi - Backlog Feb 9, 2024
@github-project-automation github-project-automation bot moved this to 🧊 Icebox in Korifi - Backlog Feb 9, 2024
@georgethebeatle georgethebeatle moved this from 🇪🇺 To do to 🧊 Icebox in Korifi - Backlog Mar 13, 2024
@georgethebeatle georgethebeatle moved this from 🧊 Icebox to 🇪🇺 To do in Korifi - Backlog Mar 13, 2024
@georgethebeatle georgethebeatle moved this from 🇪🇺 To do to 🧊 Icebox in Korifi - Backlog Mar 13, 2024
@github-project-automation github-project-automation bot moved this from 🧊 Icebox to ✅ Done in Korifi - Backlog Mar 13, 2024
@georgethebeatle
Copy link
Member Author

This change is not really worth it as the direct secret projection still needs a binding status field. Whether it is a duck type or not is not too important.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

2 participants