You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When getting details about an object, for instance deployments, daemon sets or services, the detail view will display only single line annotations and will ignore those that are multiline
To Reproduce
Steps to reproduce the behavior:
In the attached window capture you can see how a service that has two annotations is shown as having only one annotation, having the multi-line annotation (kubectl.kubernetes.io/last-applied-configuration) ignored.
Expected behavior
I expect either:
To display the full annotation in a foldable way, a multi-line annotation can take a lot of space and we don't want that
To get an indication that the annotation is there, maybe just the name equals three dots as I can always go to edit to see it
What I find misleading is that the annotation just "disappears". That can make me miss something important.
Screenshots
See above in explanation
Environment (please complete the following information):
Lens Version: 3.5.3
OS: OSX
Installation method: brew
Logs:
Not applicable
Kubeconfig:
Not applicable
Additional context
Not applicable
The text was updated successfully, but these errors were encountered:
Describe the bug
When getting details about an object, for instance deployments, daemon sets or services, the detail view will display only single line annotations and will ignore those that are multiline
To Reproduce
Steps to reproduce the behavior:
In the attached window capture you can see how a service that has two annotations is shown as having only one annotation, having the multi-line annotation (kubectl.kubernetes.io/last-applied-configuration) ignored.
Expected behavior
I expect either:
What I find misleading is that the annotation just "disappears". That can make me miss something important.
Screenshots
See above in explanation
Environment (please complete the following information):
Logs:
Not applicable
Kubeconfig:
Not applicable
Additional context
Not applicable
The text was updated successfully, but these errors were encountered: