system-dev-formations/k8s-webforce3: cnat/cnat-operator/vendor/k8s.io/kube-openapi/pkg/aggregator/aggregator.go; 4 LoC

Found a possible issue in [system-dev-formations/k8s-webforce3](https://www.github.com/system-dev-formations/k8s-webforce3) at [cnat/cnat-operator/vendor/k8s.io/kube-openapi/pkg/aggregator/aggregator.go](https://github.com/system-dev-formations/k8s-webforce3/blob/3d8a6e826b40c03c4a374b5143df5dd8bb38d49c/cnat/cnat-operator/vendor/k8s.io/kube-openapi/pkg/aggregator/aggregator.go#L82-L85)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> function call at line 83 may store a reference to v

[Click here to see the code in its original context.](https://github.com/system-dev-formations/k8s-webforce3/blob/3d8a6e826b40c03c4a374b5143df5dd8bb38d49c/cnat/cnat-operator/vendor/k8s.io/kube-openapi/pkg/aggregator/aggregator.go#L82-L85)

Click here to show the 4 line(s) of Go which triggered the analyzer.

```go
for k, v := range schema.Properties {
s.walkSchema(&v)
schema.Properties[k] = v
}

```

Click here to show extra information the analyzer produced.

```
The following graphviz dot graph describes paths through the callgraph that could lead to a function which writes a pointer argument:
digraph G {
"(walkSchema, 1)" -> {}
}

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: 3d8a6e826b40c03c4a374b5143df5dd8bb38d49c

Read cnat/cnat-operator/vendor/k8s.io/kube-openapi/pkg/aggregator/aggregator.go around lines 82-85 and inspect walkSchema. Determine whether passing &v can retain the range variable, then classify the finding as Bug, Mitigated, or Desirable Behavior; completion means leaving the appropriate reaction on the issue.

Written by the indexing model from the issue text.