Manifest for Multus 4.0.2 thick plugin support

[jdn5126]

What type of PR is this?

dependency

Which issue does this PR fix:
N/A

What does this PR do / Why do we need it:
This PRs adds a new manifest for Multus CNI v4.0.2 (https://github.com/k8snetworkplumbingwg/multus-cni/releases/tag/v4.0.2). The AWS-built image in this manifest has been validated against the latest VPC CNI. Note that we are only publishing the thick plugin currently. Additionally publishing the thin plugin is future work.

If an issue # is not available please add repro steps and logs from IPAMD/CNI showing the issue:
N/A

Testing done on this change:

Manually verified that this manifest can be applied to an existing cluster. Multus pods come up and pod IPs are assigned. The existing multus integration test checks no longer apply now that the multus architecture has changed. The existing log checks are no longer present.

Will this PR introduce any new dependencies?:

Will this break upgrades or downgrades? Has updating a running cluster been tested?:
No, Yes

Does this change require updates to the CNI daemonset config files to work?:

No

Does this PR introduce any user-facing change?:

Yes

Provide manifest for compatibility with Multus v4.0.2

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[haouc]

lgtm

[emmanuel]

Thanks for publishing an updated manifest.

Where can I find the Dockerfile(s) from which the Multus image(s) is (are) built?

[jdn5126]

@emmanuel we build using the upstream Multus Dockerfile, so for the v4.0.2 thick plugin, that is https://github.com/k8snetworkplumbingwg/multus-cni/blob/v4.0.2/images/Dockerfile.thick

We also construct the manifest from the upstream Multus manifest, so for the v4.0.2 thick plugin, that is https://github.com/k8snetworkplumbingwg/multus-cni/blob/v4.0.2/deployments/multus-daemonset-thick.yml

[emmanuel]

@jdn5126 thank you. I wonder then, where does the (AWS-specific) entrypoint.sh which is the entrypoint of the image distributed here come from?

[jdn5126]

@jdn5126 thank you. I wonder then, where does the (AWS-specific) entrypoint.sh which is the entrypoint of the image distributed here come from?

There's no entrypoint.sh in v4.0.2, but in past releases, that also came from Multus upstream: https://github.com/k8snetworkplumbingwg/multus-cni/blob/master/images/README.md#entrypointsh-parameters

The only thing AWS-specific here is that the image is hosted in private ECRs. When needed, we sometimes build Multus against an EKS Distro minimal base image and carry CVE patches. So we want to maintain that flexibility.