Release 1.13.1

[luolanzone]

No description provided.

[jianjuns]

@luolanzone : could we include this one to 1.13.1: #5380. It is needed by public cloud. @qiyueyao

[antoninbas]

@luolanzone : could we include this one to 1.13.1: #5380. It is needed by public cloud. @qiyueyao

That's a brand new API, we should not include it IMO. If Nephe needs it, they can temporarily use a commit sha from the main branch.

[jianjuns]

That's a brand new API, we should not include it IMO. If Nephe needs it, they can temporarily use a commit sha from the main branch.

So, all new API must wait for a new major release?

[antoninbas]

So, all new API must wait for a new major release?

All new APIs and new features should wait for a new minor release. It also makes it easier to track which versions have which features / APIs.

[antoninbas]

@luolanzone a new patch was added to the release: #5428

[antoninbas]

@luolanzone and another one: #5432

[luolanzone]

@antoninbas two PRs #5392 #5413 are added.

[tnqn]

That's a brand new API, we should not include it IMO. If Nephe needs it, they can temporarily use a commit sha from the main branch.

So, all new API must wait for a new major release?

If they really need an image and a tag, we could generate a 1.14 pre-release based on main branch. It also looks a bit confusing to me to backport a new API in a patch release unless it's required for critical bug or security stuff.

[luolanzone]

/test-whole-conformance
/skip-conformance
/test-networkpolicy
/test-e2e
/test-flexible-ipam-e2e
/test-multicluster-e2e
/test-multicast-e2e
/test-windows-all
/test-ipv6-all
/test-ipv6-only-all
/test-vm-e2e

[luolanzone]

/test-flexible-ipam-e2e
/test-windows-containerd-networkpolicy

[luolanzone]

/test-windows-proxyall-e2e

[luolanzone]

/test-windows-containerd-networkpolicy

[luolanzone]

/test-windows-proxyall-e2e

[luolanzone]

/test-windows-proxyall-e2e

[luolanzone]

/test-windows-proxyall-e2e

[luolanzone]

/test-windows-proxyall-e2e
/test-flexible-ipam-e2e

[luolanzone]

The testbed for test-windows-proxyall-e2e is broken, @XinShuYang is working on this.

[xliuxu]

@luolanzone maybe we can also include #5434 in 1.13.1?

[luolanzone]

/test-whole-conformance
/skip-conformance
/test-networkpolicy
/test-e2e
/test-flexible-ipam-e2e
/test-multicluster-e2e
/test-multicast-e2e
/test-windows-all
/test-ipv6-all
/test-ipv6-only-all
/test-vm-e2e

[luolanzone]

/test-windows-containerd-conformance
/test-windows-containerd-networkpolicy
/test-windows-e2e
/test-multicluster-e2e
/test-multicast-e2e
/test-flexible-ipam-e2e

[luolanzone]

/test-windows-proxyall-e2e

[luolanzone]

There is a known flexible-ipam issue tracked by #5451 , we may ignore the flexible-ipam e2e tests.

[luolanzone]

/test-windows-containerd-networkpolicy
/test-windows-proxyall-e2e

[XinShuYang]

/test-windows-containerd-networkpolicy

[XinShuYang]

@luolanzone We can skip windows docker jobs including windows-proxyall-e2e job in 1.13 release since the testbed is running on k8s 1.21.

[tnqn]

/test-multicast-e2e

[tnqn]

/skip-conformance

[luolanzone]

The multicluster e2e is passed, but the status of github is pending, we can ignore the issue for now.
@XinShuYang do you have any idea why the multicluster job didn't report the status to github?

[luolanzone]

Looks like there are two multi-cluster e2e jobs triggered, the one in public jenkins is in pending status, I suppose we can disable it? @XinShuYang @hjiajing

[XinShuYang]

@luolanzone After discussing with @hjiajing, I have disabled multicluster job on public jenkins, so now it's only available on lab jenkins.

[tnqn]

@luolanzone I have ran all cloud tests and they all passed. Please address Jianjun's comment and update the date then we can proceed. We don't need to rerun succeeded jobs.

[luolanzone]

@tnqn comment addressed and the date is updated, please help to move forward. Thanks.

[luolanzone]

@tnqn I updated the date to Sep 11 as the release date, no other changes.