Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release Proposal v2.14 #6535

Closed
floryut opened this issue Aug 14, 2020 · 16 comments
Closed

Release Proposal v2.14 #6535

floryut opened this issue Aug 14, 2020 · 16 comments
Labels
kind/support Categorizes issue or PR as a support question.

Comments

@floryut
Copy link
Member

floryut commented Aug 14, 2020

Below is a proposal for release notes:

Announcements

We are looking for maintainers, reach out in #5432.

Deprecation / Removal

  • Removed support for Fedora 29 and 30 (EOL)
  • Remove support for CoreOS Container Linux (EOL)

Major changes:

Applications

Container managers

Network

Other note worthy changes

Component versions:

  • Kubernetes v1.18.8
  • Etcd 3.4.3
  • Docker 19.03
  • containerd 1.2.13
  • Cri-O 1.18
  • CNI-plugins v0.8.7
  • Calico v3.15.2
  • Cilium 1.8.3 (See Notes)
  • Contiv 1.2.1
  • Flannel 0.12.0
  • Kube-Router 1.0.1 (see Notes)
  • Multus 3.6
  • kube-ovn 1.3.0 (see Notes)
  • Weave 2.7.0
  • CoreDNS 1.6.7
  • nodelocaldns 1.15.13
  • Helm 3.2.4
  • nginx-ingress 0.35.0
  • cert-manager 0.16.1 (see Notes)
  • Kubernetes Dashboard v2.0.4
  • Oracle OCI: v0.7.0

Known issues

TBD

Notes

  • etcd will now be upgraded and its certs renewed when using a kubeadm managed etcd (etcd_kubeadm_enabled: true)
  • Cilium: Check upgrade guide regarding update to 1.8.0
  • Kube-Router: Upgrade to 1.0.0 require an iptable flush
  • Kube-ovn is now installed in kube-system namespace, version priori to 1.0.0 should be removed manually
  • Cert-Manager: Refer to README.md prior to upgrading in your exisitng Kubernetes cluster
  • Openstack: If the nova API is before Stein, Terraform will work but the new volume type feature will not be available. If the entire cloud is upgraded to Stein or later, the new feature can be used. However if the nova versions in the cloud are mixed, with nova server API >= Stein and any nova-compute node < Stein, you will get a HTTP 409 error and VolumeTypeSupportNotYetAvailable exception.
@floryut floryut added the kind/support Categorizes issue or PR as a support question. label Aug 14, 2020
@floryut
Copy link
Member Author

floryut commented Aug 14, 2020

@Miouge1 Let's save you some time when you got back ;)

@floryut
Copy link
Member Author

floryut commented Aug 14, 2020

Pending future PR merged @ 14/08/2020 / ef3e988

@floryut floryut changed the title Release Proposal v2.14 WIP - Release Proposal v2.14 Aug 14, 2020
@lukasz-bielinski
Copy link
Contributor

@floryut what is planned release date?

@floryut
Copy link
Member Author

floryut commented Aug 14, 2020

@floryut what is planned release date?

We haven't really discuss that yet (@EppO @LuckySB @mattymo ), but should be in the coming weeks.

@hafe
Copy link
Contributor

hafe commented Aug 14, 2020

I do not know if this is worth a note:

  • cgroup manager by default set to 'systemd'

Kind of backwards incompatible

@floryut
Copy link
Member Author

floryut commented Aug 14, 2020

I do not know if this is worth a note:

  • cgroup manager by default set to 'systemd'

Kind of backwards incompatible

Agreed could be added to network notes

@huxcrux
Copy link

huxcrux commented Aug 14, 2020

I'm currently working on a PR that will fix snapshots for the Cinder CSI. There is some issue restoring a snapshot to volume when running the old v1alpha1 API. I hope to have the PR up in a few hours. If any other CSI drivers want the same fix I have in mind that everything need to be 100% reusable.

I hope I'm not to late and that we can have this feature added to the v2.14 release

@floryut
Copy link
Member Author

floryut commented Aug 14, 2020

I'm currently working on a PR that will fix snapshots for the Cinder CSI. There is some issue restoring a snapshot to volume when running the old v1alpha1 API. I hope to have the PR up in a few hours. If any other CSI drivers want the same fix I have in mind that everything need to be 100% reusable.

I hope I'm not to late and that we can have this feature added to the v2.14 release

Of course man, only wip release note, 2.14 is not till a few weeks 😃

@bmelbourne
Copy link
Contributor

I do not know if this is worth a note:

  • cgroup manager by default set to 'systemd'

Kind of backwards incompatible

Agreed could be added to network notes

FYI

I've raised PR #6563 to change the default cgroup driver to systemd for Docker.

Maybe we could consider getting this added to v2.14 to align with the CRI-O change?

@floryut
Copy link
Member Author

floryut commented Aug 24, 2020

I do not know if this is worth a note:

  • cgroup manager by default set to 'systemd'

Kind of backwards incompatible

Agreed could be added to network notes

FYI

I've raised PR #6563 to change the default cgroup driver to systemd for Docker.

Maybe we could consider getting this added to v2.14 to align with the CRI-O change?

Let's wait for it to be finish (ie: not in WIP status)

@rptaylor
Copy link
Contributor

I'm afraid I've run into an issue with #6524 on some clouds, it may be that the Openstack documentation is inaccurate in terms of the microversion requirement, or some other issue related to the use of the Openstack API, looking into it.

@Miouge1
Copy link
Contributor

Miouge1 commented Aug 27, 2020

Thank you so much for this @floryut !

@rptaylor
Copy link
Contributor

I'm pretty sure #6524 will be okay for 2.14.
The issue I ran into is described here: https://github.com/terraform-providers/terraform-provider-openstack/issues/1047
I think it is an Openstack deployment problem; if the cloud is only partially upgraded to >= Stein, the Terraform microversion check detects that the Openstack nova API can support the new feature and uses it, but the nova API checks the version of every compute node in the cloud, and if there is any older node it throws an exception. It should be fixed by fully upgrading all the nodes in the cloud to >= Stein.

@floryut
Copy link
Member Author

floryut commented Aug 28, 2020

I'm pretty sure #6524 will be okay for 2.14.
The issue I ran into is described here: terraform-providers/terraform-provider-openstack#1047
I think it is an Openstack deployment problem; if the cloud is only partially upgraded to >= Stein, the Terraform microversion check detects that the Openstack nova API can support the new feature and uses it, but the nova API checks the version of every compute node in the cloud, and if there is any older node it throws an exception. It should be fixed by fully upgrading all the nodes in the cloud to >= Stein.

Ok good to know :)

@floryut
Copy link
Member Author

floryut commented Aug 31, 2020

I do not know if this is worth a note:

  • cgroup manager by default set to 'systemd'

Kind of backwards incompatible

Agreed could be added to network notes

FYI

I've raised PR #6563 to change the default cgroup driver to systemd for Docker.

Maybe we could consider getting this added to v2.14 to align with the CRI-O change?

And done ;)

@Miouge1
Copy link
Contributor

Miouge1 commented Sep 8, 2020

Thank you so much @floryut ! v2.14.0 is out!

@Miouge1 Miouge1 closed this as completed Sep 8, 2020
@Miouge1 Miouge1 changed the title WIP - Release Proposal v2.14 Release Proposal v2.14 Sep 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question.
Projects
None yet
Development

No branches or pull requests

7 participants