frontend: Improve non dynamic clusters metadata for UI #2944
Conversation
This file contains 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
dosubot
bot
added
the
size:S
vyncent-t
added
frontend
dosubot
bot
added
the
size:S
|
Backend Code coverage changed from 65.0% to 65.2%. Change: .2% 😃. Coverage report |
vyncent-t
force-pushed
the
improve-cluster-metadata-for-ui
branch
from
280613c to
f12841b
Compare
dosubot
bot
added
size:M
|
Backend Code coverage changed from 65.0% to 65.2%. Change: .2% 😃. Coverage report |
vyncent-t
changed the title
vyncent-t
changed the title
skoeva
reviewed
Feb 25, 2025
vyncent-t
force-pushed
the
improve-cluster-metadata-for-ui
branch
from
f12841b to
38a7582
Compare
|
Backend Code coverage changed from 65.0% to 65.2%. Change: .2% 😃. Coverage report |
|
@vyncent-t can you please add How to test to the PR description? |
joaquimrocha
requested changes
Feb 28, 2025
| <Typography>{t('translation|Name')}</Typography> | ||
| {displayOriginalName && ( | ||
| <Typography variant="body2" color="textSecondary"> | ||
| {t('translation|Original name of cluster: {{ originalName }}', { |
There was a problem hiding this comment.
Just Original name: ... should be enough given the context. Reads too verbose otherwise.
Comment on lines
249
to
250
| const sourcePath = cluster.meta_data?.origin?.kubeconfig; | ||
| const kubeconfigPath = process.env.KUBECONFIG ?? sourcePath; |
There was a problem hiding this comment.
I think it should always be the meta_data case here. No the KUBECONFIG env.
| return path | ||
| }(), | ||
| }, | ||
| "originalName": context.Name, |
There was a problem hiding this comment.
I see in the /config requests from the frontend that the original name is the one being sent as the name above, so we already have the original name + custom name (in the extensions) in the frontend AFAIU.
There was a problem hiding this comment.
in the frontend when I log the end result of a cluster that has been fetched, if it has been renamed then the cluster.name is set to the customName
looking at the /config response looks like the top name is the original name but after its processed and finished for the the frontend the cluster log information is different
so I think we do have access to the original name as long as it is never renamed
There was a problem hiding this comment.
I need to understand what "after its processed and finished for the the frontend " means in this case.
Seems like we likely need to always keep the original name as the key (till we also add the kubeconfig path) for both the backend and frontend, and use the renamed name just for the display.
backend/cmd/headlamp.go
Outdated
Comment on lines
1183
to
1184
| path, _ := c.getKubeConfigPath(context.SourceStr()) | ||
| return path |
There was a problem hiding this comment.
I think the path should be set from the methods that read the cluster in the first place rather than trying to find it again here.
There was a problem hiding this comment.
moved it so that we aren't trying to find it right inside of where it is being initialized
vyncent-t
force-pushed
the
improve-cluster-metadata-for-ui
branch
from
38a7582 to
2eed250
Compare
|
Backend Code coverage changed from 65.1% to 65.2%. Change: .1% 😃. Coverage report |
vyncent-t
force-pushed
the
improve-cluster-metadata-for-ui
branch
2 times, most recently
from
108d28b to
bdaa350
Compare
|
Backend Code coverage changed from 64.9% to 65.1%. Change: .2% 😃. Coverage report |
joaquimrocha
requested changes
Mar 7, 2025
backend/cmd/headlamp.go
Outdated
| @@ -1191,6 +1191,11 @@ func (c *HeadlampConfig) getClusters() []Cluster { | |||
| continue | |||
| } | |||
|
|
|||
| kubeconfigPath, err := c.getKubeConfigPath(context.SourceStr()) | |||
There was a problem hiding this comment.
The actual path of the kubeconfig needs to be corrected. This will always give the kubeconfig we loaded headlamp with, but if we have more than one, it's not clear this will yield the correct value. So I think that the way to add it is in the methods where we load the actual kubeconfig: we should add a reference to the file's path for each cluster.
There was a problem hiding this comment.
so to confirm, we find where we load the cluster information from the kube config, create a middle func that adds the file path from that kubeconfig, and attach it to the cluster information before sending it off again?
should the same be done for the original name then? and just save the name under clusterID or something similar before sending it off?
| return path | ||
| }(), | ||
| }, | ||
| "originalName": context.Name, |
There was a problem hiding this comment.
I need to understand what "after its processed and finished for the the frontend " means in this case.
Seems like we likely need to always keep the original name as the key (till we also add the kubeconfig path) for both the backend and frontend, and use the renamed name just for the display.
vyncent-t
force-pushed
the
improve-cluster-metadata-for-ui
branch
from
bdaa350 to
935b77a
Compare
|
Backend Code coverage changed from 65.0% to 65.1%. Change: .1% 😃. Coverage report |
|
updated the branch
console log clusters in the home view now looks like
|
dosubot
bot
added
size:L
… pathID Signed-off-by: Vincent T <[email protected]>
Signed-off-by: Vincent T <[email protected]>
…clusters Signed-off-by: Vincent T <[email protected]>
…uster to a name already in use on that config file works: - the config path for renaming the config now uses a the accurate source path on user machines for backend logic (should work for multi config env) - the rename backend prevents renaming if the custom name from the request is already within the config file (either as a context name or a custom name) - add some UI to the frontend that responds when the isunique checker returns the http error Signed-off-by: Vincent T <[email protected]>
vyncent-t
force-pushed
the
improve-cluster-metadata-for-ui
branch
from
c891793 to
5f7791f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This branch replaces the need for #2747
Description
This PR aims to improve the cluster information available for clusters via the metadata tag. This PR introduces changes to the metadata field that contain the
originalNameorigin.kubeconfigandpathID`Changes include:
UI fix for App home view,
Originnow displays correct Kubeconfig pathmetadata field now includes
cluster.metadata.origin.kubeconfigandcluster.metadata.originalNameandcluster.metadata.pathIDOriginalNamenow displayed in non-dynamic cluster settingsHow to test
Namesection