Update github.com/envoyproxy/go-control-plane to get transparent socket support

[rlenglet]

Update the github.com/envoyproxy/go-control-plane dependency to get the support for the transparent socket listener flag in LDS, as specified in envoyproxy/data-plane-api#558.

Related: istio/proxy#1338
Required by: istio/istio#4654

Signed-off-by: Romain Lenglet romain@covalent.io

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[rlenglet]

I signed it!

[kyessenov]

This might be dupe of #41?
@ldemailly can you also update go-control-plane in your pruning PR?

[rlenglet]

The version of envoyproxy/data-plane-api currently in vendor through envoyproxy/go-control-plane is slightly too old. I need the API change introduced in envoyproxy/data-plane-api#558.

[kyessenov]

I think they both point to version 9fdf4bd79736a87c78b3d48b7baa84ea24be1c1a of go-control-plane which has the right API version. Getting vendor in is pretty tricky, since it requires serializing updates. I haven't finished my last update due to some issues, but me or @ldemailly could complete it, and you wouldn't need this PR.

[rlenglet]

@kyessenov OK, my bad, I didn't see that #41 was still open. Thanks!

[ldemailly]

it needs to be done on a branch