1.12 release notes: known issues bucket

[tpepper]

This issue is a bucket place holder for "known issues" additions into the 1.12 release notes.

[tpepper]

/assign @nickchase

[tpepper]

/sig release

[tpepper]

/milestone v1.12

[tpepper]

/cc @onyiny-ang @dstrebel @marpaia @guineveresaenger

[tpepper]

Possible "known issue" around reason for dropping kubernetes/enhancements#566 from v1.12 milestone. Discussions ongoing https://groups.google.com/d/topic/kubernetes-milestone-burndown/D-CP8ZAJxuI/discussion

[tpepper]

Here's the final agreed text for the CoreDNS feature #566 dropping from the v1.12 milestone:

Feature #566 enabling CoreDNS as the default for kube-up deployments was dropped from the release due to a scalability memory resource consumption issue observed. The root cause in CoreDNS remains unclear, but CoreDNS folks are investigating. If a cluster operator is considering using CoreDNS on a cluster greater than 1000 nodes, it may be necessary to give more consideration to CoreDNS pod memory resource limits and experimentally measure that memory usage versus cluster resource availability.

[dghubble]

Known issue draft for #68973

kube-controller-manager currently needs a writable --cert-dir (default is /var/run/kubernetes) for generating self-signed certificates, when no --tls-cert-file or --tls-private-key-file are provided.

[dghubble]

Known issue draft for #68986

The system:kube-controller-manager ClusterRole lacks permission to get the configmap extension-apiserver-authentication. kube-controller-manager errors if run with a service account bound to the clusterrole.

[tpepper]

Known issue text should be coming for PR #69033 which looks to be slipping to 1.12.1.

[feiskyer]

Known issue for #69033:

Runtime handler and Windows npipe protocol are not supported yet in crictl v1.11.x. Those features will be supported in crictl v1.12.0, togather with Kubernetes v1.12.1.

[dims]

time to close this since we already released 1.12.1

/close

[k8s-ci-robot]

@dims: Closing this issue.

In response to this:

time to close this since we already released 1.12.1

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.