Releases sync with upstream envoy

[Hawksbk]

Hey 👋

I have some kinda confusion with the releases of the go-control-plane, and I'm just hoping that someone may provide me a bit of guidelines about versioning and how to avoid confuses 🙏

We have a control-plane based on this package.

Recently we tried to update the version from 0.13.1 to 0.13.4, and caught by linter information about deprecating the ClusterDNS fields:

[golangci-lint: internal/resource/resource.go#L249](https://github.com/bolteu/bolt-envoy-control-plane/pull/202/files#annotation_30532653468)
SA1019: clstr.DnsRefreshRate is deprecated: Marked as deprecated in envoy/config/cluster/v3/cluster.proto. (staticcheck)

So clstr.DnsRefreshRate was deprecated in favor of extensions.cluster.dns: https://github.com/envoyproxy/envoy/blob/9aaef9877ad5cebbab0dd56a3e99da20b92ab29d/api/envoy/config/cluster/v3/cluster.proto#L956

But, the extensions.cluster.dns is presented only in the main branch of envoy and going to be a part of envoy 1.33 which is pending * https://github.com/envoyproxy/envoy/tree/main/source/extensions/clusters/dns. -> exists

• https://github.com/envoyproxy/envoy/tree/v1.32.3/source/extensions/clusters/dns - > doesn't exists

At the same time, when I checked versions of go-control-plane I saw that it's based on envoy 1.32.3:

• https://github.com/envoyproxy/go-control-plane/blob/v0.13.4/versions.yaml

So overall the question is:

• Is it supposed to be tagged on a specific version but use main branch of upstream?
• If no, is there any guidance, on how to get a better understanding of version dependencies between envoy and go-control-plane?