Kubernetes schemas have keys containing dots.
For example: io.k8s.api.core.v1.PodSecurityContext.
Taking definitions ==> io.k8s.api.core.v1.PodSpec ==> properties ==> affinity as an example:
- It is rendered as
definitions.io.k8s.api.core.v1.PodSpec.properties.affinity.
- It should probably rather be rendered as
definitions["io.k8s.api.core.v1.PodSpec"].properties.affinity, or maybe definitions."io.k8s.api.core.v1.PodSpec".properties.affinity.
By the way, with such a path the "Search nested key" function obviously doesn't work either, and should probably as well be able to understand the bracket notation for completeness.
Kubernetes schemas have keys containing dots.
For example:
io.k8s.api.core.v1.PodSecurityContext.Taking
definitions ==> io.k8s.api.core.v1.PodSpec ==> properties ==> affinityas an example:definitions.io.k8s.api.core.v1.PodSpec.properties.affinity.definitions["io.k8s.api.core.v1.PodSpec"].properties.affinity, or maybedefinitions."io.k8s.api.core.v1.PodSpec".properties.affinity.By the way, with such a path the "Search nested key" function obviously doesn't work either, and should probably as well be able to understand the bracket notation for completeness.