Introduce project IDs to OpenStack client initialization#580
Merged
Bobi-Wan merged 6 commits intogardener:mainfrom Aug 6, 2025
Merged
Introduce project IDs to OpenStack client initialization#580Bobi-Wan merged 6 commits intogardener:mainfrom
Bobi-Wan merged 6 commits intogardener:mainfrom
Conversation
…it during client creation
…his filters out available resources that belong to a project not pointed to by current client credentials (not owned by the scope). fixes: - loadbalancer - fix metric counter to properly show loadbalancers collected - network - fix metric name. Previously used the one for servers, causing incorrect data to be reported.
gardener-robot
added
needs/review
gardener-robot
added
reviewed/lgtm
gardener-robot
added
the
status/closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
With this PR, OpenStack clients retrieve the project IDs of their respective user/app credential during client creation.
This is done by creating a separate identity client, used for listing all available projects and filtering out the one with a name equal to the name configured in the client credentials. Since we also specify domain name there, we can count on there only being one project with such a name, as they should be unique per domain.
This project ID is then used to filter out most resource ListAvailable requests to be scoped to the current project (not all available ones, which might be in another project our client has access to). This excludes containers and objects, since they aren't project scoped. Extra logic might be introduced there.
Also fixed some minor issues:
Release note: