feat: New yaml file for updated CNI and CNS version

[chengch801214]

Reason for Change:
Need an update to CNI version to resolve issue with newer kernels

Issue Fixed:

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• relevant PR labels added

Notes:

[rbtr]

Are the other manifests in this directory still in use? Is this strictly a version bump? Can we just write a kustomize template and let the consumer set these versions instead of hosting a manifest copy for every release?

[chengch801214]

Are the other manifests in this directory still in use? Is this strictly a version bump? Can we just write a kustomize template and let the consumer set these versions instead of hosting a manifest copy for every release?

Yes the others are still in use. Two of them are the ones we communicated to OpenAI to use, but our tests no longer work with them, so we created two other ones with updated CNI version for two different tests.

[chengch801214]

/azp run Azure Container Networking PR

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

feedback addressed

[thomasricci]

Are the other manifests in this directory still in use? Is this strictly a version bump? Can we just write a kustomize template and let the consumer set these versions instead of hosting a manifest copy for every release?

yeah I think this makes sense. Otherwise we keep creating new files just to bump up versions. These files are purely consumer by our e2e pipeline and nobody else should be using them.

[chengch801214]

Are the other manifests in this directory still in use? Is this strictly a version bump? Can we just write a kustomize template and let the consumer set these versions instead of hosting a manifest copy for every release?

yeah I think this makes sense. Otherwise we keep creating new files just to bump up versions. These files are purely consumer by our e2e pipeline and nobody else should be using them.

I'm going to merge this PR first to unblock our E2E test. Having a customizable way to input the version is useful and can be done next time we need an update.