liferaft/kubekit: staging/src/github.com/kubekit/azure/nics.go; 7 LoC

Found a possible issue in [liferaft/kubekit](https://www.github.com/liferaft/kubekit) at [staging/src/github.com/kubekit/azure/nics.go](https://github.com/liferaft/kubekit/blob/be8b55f2165bfc82b19832e4cf8e048ad3bc4aeb/staging/src/github.com/kubekit/azure/nics.go#L51-L57)

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.

> reference to ipConfig is reassigned at line 53

[Click here to see the code in its original context.](https://github.com/liferaft/kubekit/blob/be8b55f2165bfc82b19832e4cf8e048ad3bc4aeb/staging/src/github.com/kubekit/azure/nics.go#L51-L57)

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

```go
for _, ipConfig := range *val.IPConfigurations { // *[]InterfaceIPConfiguration
if *ipConfig.Primary {
primaryIP = &ipConfig
primaryIP.PublicIPAddress = publicIPs[*val.Name]
break
}
}

```

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: be8b55f2165bfc82b19832e4cf8e048ad3bc4aeb

Start by reading staging/src/github.com/kubekit/azure/nics.go around lines 51-57 and checking the referenced commit in context. Verify the analyzer's report against Go range-loop pointer behavior and inspect any relevant tests or callers. Done means the reported behavior is either corrected with coverage or documented as intentional.

Written by the indexing model from the issue text.