This job view page is being replaced by Spyglass soon. Check out the new job view.
PRCecileRobertMichon: release notes: Remove author and PR links from Markdown
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-10-06 00:56
Elapsed5m3s
Revision44cbd61cfe2df81239e2ff9eb98ed82fe72bbd1e
Refs 2274

No Test Failures!


Error lines from build-log.txt

... skipping 99 lines ...
      --allow-dirty              If true, allow pushing dirty builds.
      --build-dir string         If provided, this directory will be uploaded as the source for the Google Cloud Build run.
      --config-dir string        Configuration directory (default ".")
      --env-passthrough string   Comma-separated list of specified environment variables to be passed to GCB as substitutions with an _ prefix. If the variable doesn't exist, the substitution will exist but be empty.
      --gcb-config string        If provided, this will be used as the name of the Google Cloud Build config file. (default "cloudbuild.yaml")
      --log-dir string           If provided, build logs will be sent to files in this directory instead of to stdout/stderr.
      --log-level string         the logging verbosity, either 'panic', 'fatal', 'error', 'warning', 'info', 'debug', 'trace' (default "info")
      --no-source                If true, no source will be uploaded with this build.
      --project string           If specified, use a non-default GCP project.
      --scratch-bucket string    The complete GCS path for Cloud Build to store scratch files (sources, logs).
      --variant string           If specified, build only the given variant. An error if no variants are defined.
--- PASS: TestRootCommand (0.00s)
PASS
coverage: 50.0% of statements
ok  	k8s.io/release/cmd/gcbuilder/cmd	0.058s	coverage: 50.0% of statements
?   	k8s.io/release/cmd/krel	[no test files]
=== RUN   TestChangelogNoArgumentsOrFlags
... skipping 807 lines ...
time="2021-10-06T00:59:43Z" level=info msg="PR #87377 seems to contain a release note"
time="2021-10-06T00:59:43Z" level=info msg="Starting to process commit 330 of 331 (99.70%): b09e35257a7997ecf2a06db11f72481834e953be"
time="2021-10-06T00:59:43Z" level=info msg="PR #87440 seems to contain a release note"
time="2021-10-06T00:59:43Z" level=info msg="Starting to process commit 331 of 331 (100.00%): 6ae1b3ea21f19419f0caaedd95005be54e558445"
time="2021-10-06T00:59:43Z" level=info msg="PR #87406 seems to contain a release note"
time="2021-10-06T00:59:43Z" level=info msg="Checking PRs for mapped data"
time="2021-10-06T00:59:43Z" level=error msg="Getting the release note from commit 52d7614a8ca5b8aebc45333b6dc8fbf86a5e7ddf (PR #87243): no matches found when parsing note text from commit string"
time="2021-10-06T00:59:43Z" level=error msg="Getting the release note from commit d1dd6cb0eff66caefe05883c247a17adc21c16a5 (PR #87509): no matches found when parsing note text from commit string"
time="2021-10-06T00:59:43Z" level=error msg="Getting the release note from commit 089d3e63e517cb7f4b764a4cd6bbb48a1d5e4b15 (PR #87072): no matches found when parsing note text from commit string"
time="2021-10-06T00:59:43Z" level=error msg="Getting the release note from commit 2b389123a5de07b8ddf0b2497f9f4f1914e0e6b5 (PR #87509): no matches found when parsing note text from commit string"
time="2021-10-06T00:59:43Z" level=info msg="finished gathering release notes in 204.806851ms"
time="2021-10-06T00:59:43Z" level=info msg="Generating TOC"
time="2021-10-06T00:59:43Z" level=info msg="Checking out master branch"
time="2021-10-06T00:59:43Z" level=info msg="Writing markdown"
time="2021-10-06T00:59:43Z" level=info msg="Adding new content to changelog file /tmp/k8s-test/test-1633481969/CHANGELOG/CHANGELOG-1.18.md "
time="2021-10-06T00:59:43Z" level=info msg="Writing HTML"
... skipping 1424 lines ...
time="2021-10-06T00:59:54Z" level=info msg="PR #90439 seems to contain a release note"
time="2021-10-06T00:59:54Z" level=info msg="Starting to process commit 713 of 714 (99.86%): f5a42d69c94b3f928ea3f9cff78cb1a81837544a"
time="2021-10-06T00:59:54Z" level=info msg="PR #94702 seems to contain a release note"
time="2021-10-06T00:59:54Z" level=info msg="Starting to process commit 714 of 714 (100.00%): daef96c3f276c8e6f3030c1dbf4edbf582784b9a"
time="2021-10-06T00:59:54Z" level=info msg="PR #94668 seems to contain a release note"
time="2021-10-06T00:59:54Z" level=info msg="Checking PRs for mapped data"
time="2021-10-06T00:59:54Z" level=error msg="Getting the release note from commit eed98104af9d1d151db91b250fa9e9499341d4ae (PR #94211): no matches found when parsing note text from commit string"
time="2021-10-06T00:59:54Z" level=error msg="Getting the release note from commit ea8de029b54a0bf867556737baacfe847b8acfde (PR #91181): no matches found when parsing note text from commit string"
time="2021-10-06T00:59:54Z" level=error msg="Getting the release note from commit d9789c4fa3ea5401f669e8293b31e09d7d9b8a6f (PR #94083): no matches found when parsing note text from commit string"
time="2021-10-06T00:59:54Z" level=error msg="Getting the release note from commit a9d1482710a4c4baf112890882f4ab3d4be158a6 (PR #94211): no matches found when parsing note text from commit string"
time="2021-10-06T00:59:54Z" level=error msg="Getting the release note from commit 7abc47d31567a981c7c350d1850d4788a8015fce (PR #93706): no matches found when parsing note text from commit string"
time="2021-10-06T00:59:54Z" level=error msg="Getting the release note from commit 8d2a2ffe014ed06b5f8971e7f3dc25ec155e44d4 (PR #94485): no matches found when parsing note text from commit string"
time="2021-10-06T00:59:54Z" level=error msg="Getting the release note from commit f588ad9c597759e45dec46b34f97824ad4323548 (PR #93843): no matches found when parsing note text from commit string"
time="2021-10-06T00:59:54Z" level=error msg="Getting the release note from commit 012b4f493b6cbc8defd8628dfdaf993fd9915f77 (PR #94485): no matches found when parsing note text from commit string"
time="2021-10-06T00:59:54Z" level=error msg="Getting the release note from commit 1b8c7585f39b879497e0538456fd6230526e6546 (PR #94726): no matches found when parsing note text from commit string"
time="2021-10-06T00:59:54Z" level=error msg="Getting the release note from commit fbd62d55af6d3ed31cdaedc43d6f19ba613056ff (PR #94726): no matches found when parsing note text from commit string"
time="2021-10-06T00:59:54Z" level=info msg="finished gathering release notes in 444.423397ms"
time="2021-10-06T00:59:54Z" level=info msg="Generating TOC"
time="2021-10-06T00:59:54Z" level=info msg="Checking out master branch"
time="2021-10-06T00:59:55Z" level=info msg="Writing markdown"
time="2021-10-06T00:59:55Z" level=info msg="Adding new content to changelog file /tmp/k8s-test/test-1633481985/CHANGELOG/CHANGELOG-1.19.md "
time="2021-10-06T00:59:55Z" level=info msg="Writing HTML"
... skipping 2 lines ...
time="2021-10-06T00:59:55Z" level=info msg="Writing JSON file to /home/prow/go/src/k8s.io/release/cmd/krel/cmd/CHANGELOG-1.19.json"
time="2021-10-06T00:59:55Z" level=info msg="Committing changes"
time="2021-10-06T00:59:55Z" level=info msg="Adding CHANGELOG/CHANGELOG-1.19.md to repository"
time="2021-10-06T00:59:55Z" level=info msg="Adding CHANGELOG/README.md to repository"
time="2021-10-06T00:59:55Z" level=info msg="Committing changes to main branch in repository"
    changelog_test.go:46: 
        	Error Trace:	changelog_test.go:46
        	            				changelog_test.go:140
        	Error:      	"<!DOCTYPE html>\n<html>\n  <head>\n    <meta charset=\"utf-8\" />\n    <meta name=\"viewport\" content=\"width=device-width\" />\n    <title>v1.19.0-alpha.1</title>\n    <style type=\"text/css\">\n      table,\n      th,\n      tr,\n      td {\n        border: 1px solid gray;\n        border-collapse: collapse;\n        padding: 5px;\n      }\n    </style>\n  </head>\n  <body>\n    <h1>v1.19.0-alpha.1</h1>\n<h2>Changelog since v1.18.0</h2>\n<h2>Changes by Kind</h2>\n<h3>Deprecation</h3>\n<ul>\n<li>Kubeadm: remove the deprecated &quot;kubeadm alpha kubelet config enable-dynamic&quot; command. To continue using the feature please defer to the guide for &quot;Dynamic Kubelet Configuration&quot; at k8s.io. This change also removes the parent command &quot;kubeadm alpha kubelet&quot; as there are no more sub-commands under it for the time being. (#94668, @neolit123) [SIG Cluster Lifecycle]</li>\n<li>Kubeadm: remove the deprecated --kubelet-config flag for the command &quot;kubeadm upgrade node&quot; (#94869, @neolit123) [SIG Cluster Lifecycle]</li>\n<li>Kubelet's deprecated endpoint <code>metrics/resource/v1alpha1</code> has been removed, please adopt to <code>metrics/resource</code>. (#94272, @RainbowMango) [SIG Instrumentation and Node]</li>\n<li>The v1alpha1 PodPreset API and admission plugin has been removed with no built-in replacement. Admission webhooks can be used to modify pods on creation. (#94090, @deads2k) [SIG API Machinery, Apps, CLI, Cloud Provider, Scalability and Testing]</li>\n</ul>\n<h3>API Change</h3>\n<ul>\n<li>A new <code>nofuzz</code> go build tag now disables gofuzz support. Release binaries enable this. (#92491, @BenTheElder) [SIG API Machinery]</li>\n<li>External facing API podresources is now available under k8s.io/kubelet/pkg/apis/ (#92632, @RenaudWasTaken) [SIG Node and Testing]</li>\n<li>Fix conversions for custom metrics. (#94481, @wojtek-t) [SIG API Machinery and Instrumentation]</li>\n<li>Kube-controller-manager: volume plugins can be restricted from contacting local and loopback addresses by setting <code>--volume-host-allow-local-loopback=false</code>, or from contacting specific CIDR ranges by setting <code>--volume-host-cidr-denylist</code> (for example, <code>--volume-host-cidr-denylist=127.0.0.1/28,feed::/16</code>) (#91785, @mattcary) [SIG API Machinery, Apps, Auth, CLI, Network, Node, Storage and Testing]</li>\n<li>Migrate scheduler, controller-manager and cloud-controller-manager to use LeaseLock (#94603, @wojtek-t) [SIG API Machinery, Apps, Cloud Provider and Scheduling]</li>\n<li>Modify DNS-1123 error messages to indicate that RFC 1123 is not followed exactly (#94182, @mattfenwick) [SIG API Machinery, Apps, Auth, Network and Node]</li>\n<li>The ServiceAccountIssuerDiscovery feature gate is now Beta and enabled by default. (#91921, @mtaufen) [SIG Auth]</li>\n<li>WinOverlay feature graduated to beta (#94807, @ksubrmnn) [SIG Windows]</li>\n</ul>\n<h3>Feature</h3>\n<ul>\n<li>Add metrics for azure service operations (route and loadbalancer). (#94124, @nilo19) [SIG Cloud Provider and Instrumentation]</li>\n<li>Add network rule support in Azure account creation (#94239, @andyzhangx) [SIG Cloud Provider]</li>\n<li>Kubeadm: Add a preflight check that the control-plane node has at least 1700MB of RAM (#93275, @xlgao-zju) [SIG Cluster Lifecycle]</li>\n<li>Kubeadm: add the &quot;--cluster-name&quot; flag to the &quot;kubeadm alpha kubeconfig user&quot; to allow configuring the cluster name in the generated kubeconfig file (#93992, @prabhu43) [SIG Cluster Lifecycle]</li>\n<li>Kubeadm: add the &quot;--kubeconfig&quot; flag to the &quot;kubeadm init phase upload-certs&quot; command to allow users to pass a custom location for a kubeconfig file. (#94765, @zhanw15) [SIG Cluster Lifecycle]</li>\n<li>Kubeadm: make etcd pod request 100m CPU, 100Mi memory and 100Mi ephemeral_storage by default (#94479, @knight42) [SIG Cluster Lifecycle]</li>\n<li>Kubeadm: make the command &quot;kubeadm alpha kubeconfig user&quot; accept a &quot;--config&quot; flag and remove the following flags:\n<ul>\n<li>apiserver-advertise-address / apiserver-bind-port: use either localAPIEndpoint from InitConfiguration or controlPlaneEndpoint from ClusterConfiguration.</li>\n<li>cluster-name: use clusterName from ClusterConfiguration</li>\n<li>cert-dir: use certificatesDir from ClusterConfiguration (#94879, @knight42) [SIG Cluster Lifecycle]</li>\n</ul>\n</li>\n<li>Kubemark now supports both real and hollow nodes in a single cluster. (#93201, @ellistarn) [SIG Scalability]</li>\n<li>Kubernetes is now built using go1.15.2\n<ul>\n<li>\n<p>build: Update to <a href=\"mailto:k/repo-infra@v0.1.1\">k/repo-infra@v0.1.1</a> (supports go1.15.2)</p>\n</li>\n<li>\n<p>build: Use go-runner:buster-v2.0.1 (built using go1.15.1)</p>\n</li>\n<li>\n<p>bazel: Replace --features with Starlark build settings flag</p>\n</li>\n<li>\n<p>hack/lib/util.sh: some bash cleanups</p>\n<ul>\n<li>switched one spot to use kube::logging</li>\n<li>make kube::util::find-binary return an error when it doesn't find\nanything so that hack scripts fail fast instead of with '' binary not\nfound errors.</li>\n<li>this required deleting some genfeddoc stuff. the binary no longer\nexists in k/k repo since we removed federation/, and I don't see it\nin <a href=\"https://github.com/kubernetes-sigs/kubefed/\">https://github.com/kubernetes-sigs/kubefed/</a> either. I'm assuming\nthat it's gone for good now.</li>\n</ul>\n</li>\n<li>\n<p>bazel: output go_binary rule directly from go_binary_conditional_pure</p>\n<p>From: @mikedanese:\nInstead of aliasing. Aliases are annoying in a number of ways. This is\nspecifically bugging me now because they make the action graph harder to\nanalyze programmatically. By using aliases here, we would need to handle\npotentially aliased go_binary targets and dereference to the effective\ntarget.</p>\n<p>The comment references an issue with <code>pure = select(...)</code> which appears\nto be resolved considering this now builds.</p>\n</li>\n<li>\n<p>make kube::util::find-binary not dependent on bazel-out/ structure</p>\n<p>Implement an aspect that outputs go_build_mode metadata for go binaries,\nand use that during binary selection. (#94449, @justaugustus) [SIG Architecture, CLI, Cluster Lifecycle, Node, Release and Testing]</p>\n</li>\n</ul>\n</li>\n<li>Only update Azure data disks when attach/detach (#94265, @andyzhangx) [SIG Cloud Provider]</li>\n<li>Promote SupportNodePidsLimit to GA to provide node to pod pid isolation\nPromote SupportPodPidsLimit to GA to provide ability to limit pids per pod (#94140, @derekwaynecarr) [SIG Node and Testing]</li>\n<li>Support [service.beta.kubernetes.io/azure-pip-ip-tags] annotations to allow customers to specify ip-tags to influence public-ip creation in Azure [Tag1=Value1, Tag2=Value2, etc.] (#94114, @MarcPow) [SIG Cloud Provider]</li>\n</ul>\n<h3>Documentation</h3>\n<ul>\n<li>Kubelet: remove alpha warnings for CNI flags. (#94508, @andrewsykim) [SIG Network and Node]</li>\n</ul>\n<h3>Bug or Regression</h3>\n<ul>\n<li>\n<p>Add kubectl wait  --ignore-not-found flag (#90969, @zhouya0) [SIG CLI]</p>\n</li>\n<li>\n<p>Adding fix to the statefulset controller to wait for pvc deletion before creating pods. (#93457, @ymmt2005) [SIG Apps]</p>\n</li>\n<li>\n<p>Azure ARM client: don't segfault on empty response and http error (#94078, @bpineau) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Azure: fix a bug that kube-controller-manager would panic if wrong Azure VMSS name is configured (#94306, @knight42) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Both apiserver_request_duration_seconds metrics and RequestReceivedTimestamp field of an audit event take\ninto account the time a request spends in the apiserver request filters. (#94903, @tkashem) [SIG API Machinery, Auth and Instrumentation]</p>\n</li>\n<li>\n<p>Build/lib/release: Explicitly use '--platform' in building server images</p>\n<p>When we switched to go-runner for building the apiserver,\ncontroller-manager, and scheduler server components, we no longer\nreference the individual architectures in the image names, specifically\nin the 'FROM' directive of the server image Dockerfiles.</p>\n<p>As a result, server images for non-amd64 images copy in the go-runner\namd64 binary instead of the go-runner that matches that architecture.</p>\n<p>This commit explicitly sets the '--platform=linux/${arch}' to ensure\nwe're pulling the correct go-runner arch from the manifest list.</p>\n<p>Before:\n<code>FROM ${base_image}</code></p>\n<p>After:\n<code>FROM --platform=linux/${arch} ${base_image}</code> (#94552, @justaugustus) [SIG Release]</p>\n</li>\n<li>\n<p>CSIDriver object can be deployed during volume attachment. (#93710, @Jiawei0227) [SIG Apps, Node, Storage and Testing]</p>\n</li>\n<li>\n<p>Do not fail sorting empty elements. (#94666, @soltysh) [SIG CLI]</p>\n</li>\n<li>\n<p>Dual-stack: make nodeipam compatible with existing single-stack clusters when dual-stack feature gate become enabled by default (#90439, @SataQiu) [SIG API Machinery]</p>\n</li>\n<li>\n<p>Ensure backoff step is set to 1 for Azure armclient. (#94180, @feiskyer) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Ensure getPrimaryInterfaceID not panic when network interfaces for Azure VMSS are null (#94355, @feiskyer) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Fix HandleCrash order (#93108, @lixiaobing1) [SIG API Machinery]</p>\n</li>\n<li>\n<p>Fix a concurrent map writes error in kubelet (#93773, @knight42) [SIG Node]</p>\n</li>\n<li>\n<p>Fix a regression where kubeadm bails out with a fatal error when an optional version command line argument is supplied to the &quot;kubeadm upgrade plan&quot; command (#94421, @rosti) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Fix azure file migration panic (#94853, @andyzhangx) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Fix bug where loadbalancer deletion gets stuck because of missing resource group #75198 (#93962, @phiphi282) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Fix etcd_object_counts metric reported by kube-apiserver (#94773, @tkashem) [SIG API Machinery]</p>\n</li>\n<li>\n<p>Fix incorrectly reported verbs for kube-apiserver metrics for CRD objects (#93523, @wojtek-t) [SIG API Machinery and Instrumentation]</p>\n</li>\n<li>\n<p>Fix kubectl SchemaError on CRDs with schema using x-kubernetes-preserve-unknown-fields on array types. (#94888, @sttts) [SIG API Machinery]</p>\n</li>\n<li>\n<p>Fix missing csi annotations on node during parallel csinode update. (#94389, @pacoxu) [SIG Storage]</p>\n</li>\n<li>\n<p>Fix the <code>cloudprovider_azure_api_request_duration_seconds</code> metric buckets to correctly capture the latency metrics. Previously, the majority of the calls would fall in the &quot;+Inf&quot; bucket. (#94873, @marwanad) [SIG Cloud Provider and Instrumentation]</p>\n</li>\n<li>\n<p>Fix: azure disk resize error if source does not exist (#93011, @andyzhangx) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Fix: detach azure disk broken on Azure Stack (#94885, @andyzhangx) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Fix: use sensitiveOptions on Windows mount (#94126, @andyzhangx) [SIG Cloud Provider and Storage]</p>\n</li>\n<li>\n<p>Fixed Ceph RBD volume expansion when no ceph.conf exists (#92027, @juliantaylor) [SIG Storage]</p>\n</li>\n<li>\n<p>Fixed a bug where improper storage and comparison of endpoints led to excessive API traffic from the endpoints controller (#94112, @damemi) [SIG Apps, Network and Testing]</p>\n</li>\n<li>\n<p>Fixed a panic in kubectl debug when pod has multiple init containers or ephemeral containers (#94580, @kiyoshim55) [SIG CLI]</p>\n</li>\n<li>\n<p>Fixed a regression that sometimes prevented <code>kubectl portforward</code> to work when TCP and UDP services were configured on the same port (#94728, @amorenoz) [SIG CLI]</p>\n</li>\n<li>\n<p>Fixed bug in reflector that couldn't recover from &quot;Too large resource version&quot; errors with API servers 1.17.0-1.18.5 (#94316, @janeczku) [SIG API Machinery]</p>\n</li>\n<li>\n<p>Fixed bug where kubectl top pod output is not sorted when --sort-by and --containers flags are used together (#93692, @brianpursley) [SIG CLI]</p>\n</li>\n<li>\n<p>Fixed kubelet creating extra sandbox for pods with RestartPolicyOnFailure after all containers succeeded (#92614, @tnqn) [SIG Node and Testing]</p>\n</li>\n<li>\n<p>Fixes a bug where EndpointSlices would not be recreated after rapid Service recreation. (#94730, @robscott) [SIG Apps, Network and Testing]</p>\n</li>\n<li>\n<p>Fixes a race condition in kubelet pod handling (#94751, @auxten) [SIG Node]</p>\n</li>\n<li>\n<p>Fixes an issue proxying to ipv6 pods without specifying a port (#94834, @liggitt) [SIG API Machinery and Network]</p>\n</li>\n<li>\n<p>Ignore root user check when windows pod starts (#92355, @wawa0210) [SIG Node and Windows]</p>\n</li>\n<li>\n<p>Increased maximum IOPS of AWS EBS io1 volumes to 64,000 (current AWS maximum). (#90014, @jacobmarble) [SIG Cloud Provider and Storage]</p>\n</li>\n<li>\n<p>K8s.io/apimachinery: runtime.DefaultUnstructuredConverter.FromUnstructured now handles converting integer fields to typed float values (#93250, @liggitt) [SIG API Machinery]</p>\n</li>\n<li>\n<p>Kube-proxy now trims extra spaces found in loadBalancerSourceRanges to match Service validation. (#94107, @robscott) [SIG Network]</p>\n</li>\n<li>\n<p>Kubeadm now makes sure the etcd manifest is regenerated upon upgrade even when no etcd version change takes place (#94395, @rosti) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Kubeadm: avoid a panic when determining if the running version of CoreDNS is supported during upgrades (#94299, @zouyee) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Kubeadm: ensure &quot;kubeadm reset&quot; does not unmount the root &quot;/var/lib/kubelet&quot; directory if it is mounted by the user (#93702, @thtanaka) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Kubeadm: ensure the etcd data directory is created with 0700 permissions during control-plane init and join (#94102, @neolit123) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Kubeadm: fix the bug that kubeadm tries to call 'docker info' even if the CRI socket was for another CR (#94555, @SataQiu) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Kubeadm: make the kubeconfig files for the kube-controller-manager and kube-scheduler use the LocalAPIEndpoint instead of the ControlPlaneEndpoint. This makes kubeadm clusters more reseliant to version skew problems during immutable upgrades: <a href=\"https://kubernetes.io/docs/setup/release/version-skew-policy/#kube-controller-manager-kube-scheduler-and-cloud-controller-manager\">https://kubernetes.io/docs/setup/release/version-skew-policy/#kube-controller-manager-kube-scheduler-and-cloud-controller-manager</a> (#94398, @neolit123) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Kubeadm: relax the validation of kubeconfig server URLs. Allow the user to define custom kubeconfig server URLs without erroring out during validation of existing kubeconfig files (e.g. when using external CA mode). (#94816, @neolit123) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Kubelet: assume that swap is disabled when <code>/proc/swaps</code> does not exist (#93931, @SataQiu) [SIG Node]</p>\n</li>\n<li>\n<p>New Azure instance types do now have correct max data disk count information. (#94340, @ialidzhikov) [SIG Cloud Provider and Storage]</p>\n</li>\n<li>\n<p>Require feature flag CustomCPUCFSQuotaPeriod if setting a non-default cpuCFSQuotaPeriod in kubelet config. (#94687, @karan) [SIG Node]</p>\n</li>\n<li>\n<p>The <code>/debug/api_priority_and_fairness/dump_requests</code> path at an apiserver will no longer return a phantom line for each exempt priority level. (#93406, @MikeSpreitzer) [SIG API Machinery]</p>\n</li>\n<li>\n<p>The kubelet recognizes the --containerd-namespace flag to configure the namespace used by cadvisor. (#87054, @changyaowei) [SIG Node]</p>\n</li>\n<li>\n<p>Update Calico to v3.15.2 (#94241, @lmm) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Update default etcd server version to 3.4.13 (#94287, @jingyih) [SIG API Machinery, Cloud Provider, Cluster Lifecycle and Testing]</p>\n</li>\n<li>\n<p>Use NLB Subnet CIDRs instead of VPC CIDRs in Health Check SG Rules (#93515, @t0rr3sp3dr0) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Users will see increase in time for deletion of pods and also guarantee that removal of pod from api server  would mean deletion of all the resources from container runtime. (#92817, @kmala) [SIG Node]</p>\n</li>\n<li>\n<p>Very large patches may now be specified to <code>kubectl patch</code> with the <code>--patch-file</code> flag instead of including them directly on the command line. The <code>--patch</code> and <code>--patch-file</code> flags are mutually exclusive. (#93548, @smarterclayton) [SIG CLI]</p>\n</li>\n</ul>\n<h3>Other (Cleanup or Flake)</h3>\n<ul>\n<li>Adds a bootstrapping ClusterRole, ClusterRoleBinding and group for /metrics, /livez/<em>, /readyz/</em>, &amp; /healthz/* endpoints. (#93311, @logicalhan) [SIG API Machinery, Auth, Cloud Provider and Instrumentation]</li>\n<li>Base-images: Update to debian-iptables:buster-v1.3.0\n<ul>\n<li>Uses iptables 1.8.5</li>\n<li>base-images: Update to debian-base:buster-v1.2.0</li>\n<li>cluster/images/etcd: Build etcd:3.4.13-1 image\n<ul>\n<li>Uses debian-base:buster-v1.2.0 (#94733, @justaugustus) [SIG API Machinery, Release and Testing]</li>\n</ul>\n</li>\n</ul>\n</li>\n<li>Fix kubelet to properly log when a container is started. Before, sometimes the log said that a container is dead and was restarted when it was started for the first time. This only happened when using pods with initContainers and regular containers. (#91469, @rata) [SIG Node]</li>\n<li>Fixes the flooding warning messages about setting volume ownership for configmap/secret volumes (#92878, @jvanz) [SIG Instrumentation, Node and Storage]</li>\n<li>Fixes the message about no auth for metrics in scheduler. (#94035, @zhouya0) [SIG Scheduling]</li>\n<li>Kubeadm: Separate argument key/value in log msg (#94016, @mrueg) [SIG Cluster Lifecycle]</li>\n<li>Kubeadm: remove support for the &quot;ci/k8s-master&quot; version label. This label has been removed in the Kubernetes CI release process and would no longer work in kubeadm. You can use the &quot;ci/latest&quot; version label instead. See kubernetes/test-infra#18517 (#93626, @vikkyomkar) [SIG Cluster Lifecycle]</li>\n<li>Kubeadm: remove the CoreDNS check for known image digests when applying the addon (#94506, @neolit123) [SIG Cluster Lifecycle]</li>\n<li>Lock ExternalPolicyForExternalIP to default, this feature gate will be removed in 1.22. (#94581, @knabben) [SIG Network]</li>\n<li>Service.beta.kubernetes.io/azure-load-balancer-disable-tcp-reset is removed.  All Standard load balancers will always enable tcp resets. (#94297, @MarcPow) [SIG Cloud Provider]</li>\n<li>Stop propagating SelfLink (deprecated in 1.16) in kube-apiserver (#94397, @wojtek-t) [SIG API Machinery and Testing]</li>\n<li>Strip unnecessary security contexts on Windows (#93475, @ravisantoshgudimetla) [SIG Node, Testing and Windows]</li>\n<li>Update CNI plugins to v0.8.7 (#94367, @justaugustus) [SIG Cloud Provider, Network, Node, Release and Testing]</li>\n<li>Update cri-tools to <a href=\"https://github.com/kubernetes-sigs/cri-tools/releases/tag/v1.19.0\">v1.19.0</a> (#94307, @xmudrii) [SIG Cloud Provider]</li>\n<li>Update etcd client side to v3.4.13 (#94259, @jingyih) [SIG API Machinery and Cloud Provider]</li>\n<li><code>kubectl get ingress</code> now prefers the <code>networking.k8s.io/v1</code> over <code>extensions/v1beta1</code> (deprecated since v1.14). To explicitly request the deprecated version, use <code>kubectl get ingress.v1beta1.extensions</code>. (#94309, @liggitt) [SIG API Machinery and CLI]</li>\n</ul>\n\n  </body>\n</html>" does not contain "<!DOCTYPE html>\n<html>\n  <head>\n    <meta charset=\"utf-8\" />\n    <meta name=\"viewport\" content=\"width=device-width\" />\n    <title>v1.19.0-alpha.1</title>\n    <style type=\"text/css\">\n      table,\n      th,\n      tr,\n      td {\n        border: 1px solid gray;\n        border-collapse: collapse;\n        padding: 5px;\n      }\n    </style>\n  </head>\n  <body>\n    <h1>v1.19.0-alpha.1</h1>\n<h2>Changelog since v1.18.0</h2>\n<h2>Changes by Kind</h2>\n<h3>Deprecation</h3>\n<ul>\n<li>Kubeadm: remove the deprecated &quot;kubeadm alpha kubelet config enable-dynamic&quot; command. To continue using the feature please defer to the guide for &quot;Dynamic Kubelet Configuration&quot; at k8s.io. This change also removes the parent command &quot;kubeadm alpha kubelet&quot; as there are no more sub-commands under it for the time being. (#94668, @neolit123) [SIG Cluster Lifecycle]</li>\n<li>Kubeadm: remove the deprecated --kubelet-config flag for the command &quot;kubeadm upgrade node&quot; (#94869, @neolit123) [SIG Cluster Lifecycle]</li>\n<li>Kubelet's deprecated endpoint <code>metrics/resource/v1alpha1</code> has been removed, please adopt to <code>metrics/resource</code>. (#94272, @RainbowMango) [SIG Instrumentation and Node]</li>\n<li>The v1alpha1 PodPreset API and admission plugin has been removed with no built-in replacement. Admission webhooks can be used to modify pods on creation. (#94090, @deads2k) [SIG API Machinery, Apps, CLI, Cloud Provider, Scalability and Testing]</li>\n</ul>\n<h3>API Change</h3>\n<ul>\n<li>A new <code>nofuzz</code> go build tag now disables gofuzz support. Release binaries enable this. (#92491, @BenTheElder) [SIG API Machinery]</li>\n<li>External facing API podresources is now available under k8s.io/kubelet/pkg/apis/ (#92632, @RenaudWasTaken) [SIG Node and Testing]</li>\n<li>Fix conversions for custom metrics. (#94481, @wojtek-t) [SIG API Machinery and Instrumentation]</li>\n<li>Kube-controller-manager: volume plugins can be restricted from contacting local and loopback addresses by setting <code>--volume-host-allow-local-loopback=false</code>, or from contacting specific CIDR ranges by setting <code>--volume-host-cidr-denylist</code> (for example, <code>--volume-host-cidr-denylist=127.0.0.1/28,feed::/16</code>) (#91785, @mattcary) [SIG API Machinery, Apps, Auth, CLI, Network, Node, Storage and Testing]</li>\n<li>Migrate scheduler, controller-manager and cloud-controller-manager to use LeaseLock (#94603, @wojtek-t) [SIG API Machinery, Apps, Cloud Provider and Scheduling]</li>\n<li>Modify DNS-1123 error messages to indicate that RFC 1123 is not followed exactly (#94182, @mattfenwick) [SIG API Machinery, Apps, Auth, Network and Node]</li>\n<li>The ServiceAccountIssuerDiscovery feature gate is now Beta and enabled by default. (#91921, @mtaufen) [SIG Auth]</li>\n<li>WinOverlay feature graduated to beta (#94807, @ksubrmnn) [SIG Windows]</li>\n</ul>\n<h3>Feature</h3>\n<ul>\n<li>Add metrics for azure service operations (route and loadbalancer). (#94124, @nilo19) [SIG Cloud Provider and Instrumentation]</li>\n<li>Add network rule support in Azure account creation (#94239, @andyzhangx) [SIG Cloud Provider]</li>\n<li>Kubeadm: Add a preflight check that the control-plane node has at least 1700MB of RAM (#93275, @xlgao-zju) [SIG Cluster Lifecycle]</li>\n<li>Kubeadm: add the &quot;--cluster-name&quot; flag to the &quot;kubeadm alpha kubeconfig user&quot; to allow configuring the cluster name in the generated kubeconfig file (#93992, @prabhu43) [SIG Cluster Lifecycle]</li>\n<li>Kubeadm: add the &quot;--kubeconfig&quot; flag to the &quot;kubeadm init phase upload-certs&quot; command to allow users to pass a custom location for a kubeconfig file. (#94765, @zhanw15) [SIG Cluster Lifecycle]</li>\n<li>Kubeadm: make etcd pod request 100m CPU, 100Mi memory and 100Mi ephemeral_storage by default (#94479, @knight42) [SIG Cluster Lifecycle]</li>\n<li>Kubeadm: make the command &quot;kubeadm alpha kubeconfig user&quot; accept a &quot;--config&quot; flag and remove the following flags:\n<ul>\n<li>apiserver-advertise-address / apiserver-bind-port: use either localAPIEndpoint from InitConfiguration or controlPlaneEndpoint from ClusterConfiguration.</li>\n<li>cluster-name: use clusterName from ClusterConfiguration</li>\n<li>cert-dir: use certificatesDir from ClusterConfiguration (#94879, @knight42) [SIG Cluster Lifecycle]</li>\n</ul>\n</li>\n<li>Kubemark now supports both real and hollow nodes in a single cluster. (#93201, @ellistarn) [SIG Scalability]</li>\n<li>Kubernetes is now built using go1.15.2\n<ul>\n<li>\n<p>build: Update to <a href=\"mailto:k/repo-infra@v0.1.1\">k/repo-infra@v0.1.1</a> (supports go1.15.2)</p>\n</li>\n<li>\n<p>build: Use go-runner:buster-v2.0.1 (built using go1.15.1)</p>\n</li>\n<li>\n<p>bazel: Replace --features with Starlark build settings flag</p>\n</li>\n<li>\n<p>hack/lib/util.sh: some bash cleanups</p>\n<ul>\n<li>switched one spot to use kube::logging</li>\n<li>make kube::util::find-binary return an error when it doesn't find\nanything so that hack scripts fail fast instead of with '' binary not\nfound errors.</li>\n<li>this required deleting some genfeddoc stuff. the binary no longer\nexists in k/k repo since we removed federation/, and I don't see it\nin <a href=\"https://github.com/kubernetes-sigs/kubefed/\">https://github.com/kubernetes-sigs/kubefed/</a> either. I'm assuming\nthat it's gone for good now.</li>\n</ul>\n</li>\n<li>\n<p>bazel: output go_binary rule directly from go_binary_conditional_pure</p>\n<p>From: @mikedanese:\nInstead of aliasing. Aliases are annoying in a number of ways. This is\nspecifically bugging me now because they make the action graph harder to\nanalyze programmatically. By using aliases here, we would need to handle\npotentially aliased go_binary targets and dereference to the effective\ntarget.</p>\n<p>The comment references an issue with <code>pure = select(...)</code> which appears\nto be resolved considering this now builds.</p>\n</li>\n<li>\n<p>make kube::util::find-binary not dependent on bazel-out/ structure</p>\n<p>Implement an aspect that outputs go_build_mode metadata for go binaries,\nand use that during binary selection. (#94449, @justaugustus) [SIG Architecture, CLI, Cluster Lifecycle, Node, Release and Testing]</p>\n</li>\n</ul>\n</li>\n<li>Only update Azure data disks when attach/detach (#94265, @andyzhangx) [SIG Cloud Provider]</li>\n<li>Promote SupportNodePidsLimit to GA to provide node to pod pid isolation\nPromote SupportPodPidsLimit to GA to provide ability to limit pids per pod (#94140, @derekwaynecarr) [SIG Node and Testing]</li>\n<li>Support [service.beta.kubernetes.io/azure-pip-ip-tags] annotations to allow customers to specify ip-tags to influence public-ip creation in Azure [Tag1=Value1, Tag2=Value2, etc.] (#94114, @MarcPow) [SIG Cloud Provider]</li>\n</ul>\n<h3>Documentation</h3>\n<ul>\n<li>Kubelet: remove alpha warnings for CNI flags. (#94508, @andrewsykim) [SIG Network and Node]</li>\n</ul>\n<h3>Bug or Regression</h3>\n<ul>\n<li>\n<p>Add kubectl wait  --ignore-not-found flag (#90969, @zhouya0) [SIG CLI]</p>\n</li>\n<li>\n<p>Adding fix to the statefulset controller to wait for pvc deletion before creating pods. (#93457, @ymmt2005) [SIG Apps]</p>\n</li>\n<li>\n<p>Azure ARM client: don't segfault on empty response and http error (#94078, @bpineau) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Azure: fix a bug that kube-controller-manager would panic if wrong Azure VMSS name is configured (#94306, @knight42) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Both apiserver_request_duration_seconds metrics and RequestReceivedTimestamp field of an audit event take\ninto account the time a request spends in the apiserver request filters. (#94903, @tkashem) [SIG API Machinery, Auth and Instrumentation]</p>\n</li>\n<li>\n<p>Build/lib/release: Explicitly use '--platform' in building server images</p>\n<p>When we switched to go-runner for building the apiserver,\ncontroller-manager, and scheduler server components, we no longer\nreference the individual architectures in the image names, specifically\nin the 'FROM' directive of the server image Dockerfiles.</p>\n<p>As a result, server images for non-amd64 images copy in the go-runner\namd64 binary instead of the go-runner that matches that architecture.</p>\n<p>This commit explicitly sets the '--platform=linux/${arch}' to ensure\nwe're pulling the correct go-runner arch from the manifest list.</p>\n<p>Before:\n<code>FROM ${base_image}</code></p>\n<p>After:\n<code>FROM --platform=linux/${arch} ${base_image}</code> (#94552, @justaugustus) [SIG Release]</p>\n</li>\n<li>\n<p>CSIDriver object can be deployed during volume attachment. (#93710, @Jiawei0227) [SIG Apps, Node, Storage and Testing]</p>\n</li>\n<li>\n<p>Do not fail sorting empty elements. (#94666, @soltysh) [SIG CLI]</p>\n</li>\n<li>\n<p>Dual-stack: make nodeipam compatible with existing single-stack clusters when dual-stack feature gate become enabled by default (#90439, @SataQiu) [SIG API Machinery]</p>\n</li>\n<li>\n<p>Ensure backoff step is set to 1 for Azure armclient. (#94180, @feiskyer) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Ensure getPrimaryInterfaceID not panic when network interfaces for Azure VMSS are null (#94355, @feiskyer) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Fix HandleCrash order (#93108, @lixiaobing1) [SIG API Machinery]</p>\n</li>\n<li>\n<p>Fix a concurrent map writes error in kubelet (#93773, @knight42) [SIG Node]</p>\n</li>\n<li>\n<p>Fix a regression where kubeadm bails out with a fatal error when an optional version command line argument is supplied to the &quot;kubeadm upgrade plan&quot; command (#94421, @rosti) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Fix azure file migration panic (#94853, @andyzhangx) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Fix bug where loadbalancer deletion gets stuck because of missing resource group #75198 (#93962, @phiphi282) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Fix etcd_object_counts metric reported by kube-apiserver (#94773, @tkashem) [SIG API Machinery]</p>\n</li>\n<li>\n<p>Fix incorrectly reported verbs for kube-apiserver metrics for CRD objects (#93523, @wojtek-t) [SIG API Machinery and Instrumentation]</p>\n</li>\n<li>\n<p>Fix kubectl SchemaError on CRDs with schema using x-kubernetes-preserve-unknown-fields on array types. (#94888, @sttts) [SIG API Machinery]</p>\n</li>\n<li>\n<p>Fix missing csi annotations on node during parallel csinode update. (#94389, @pacoxu) [SIG Storage]</p>\n</li>\n<li>\n<p>Fix the <code>cloudprovider_azure_api_request_duration_seconds</code> metric buckets to correctly capture the latency metrics. Previously, the majority of the calls would fall in the &quot;+Inf&quot; bucket. (#94873, @marwanad) [SIG Cloud Provider and Instrumentation]</p>\n</li>\n<li>\n<p>Fix: azure disk resize error if source does not exist (#93011, @andyzhangx) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Fix: detach azure disk broken on Azure Stack (#94885, @andyzhangx) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Fix: use sensitiveOptions on Windows mount (#94126, @andyzhangx) [SIG Cloud Provider and Storage]</p>\n</li>\n<li>\n<p>Fixed Ceph RBD volume expansion when no ceph.conf exists (#92027, @juliantaylor) [SIG Storage]</p>\n</li>\n<li>\n<p>Fixed a bug where improper storage and comparison of endpoints led to excessive API traffic from the endpoints controller (#94112, @damemi) [SIG Apps, Network and Testing]</p>\n</li>\n<li>\n<p>Fixed a panic in kubectl debug when pod has multiple init containers or ephemeral containers (#94580, @kiyoshim55) [SIG CLI]</p>\n</li>\n<li>\n<p>Fixed a regression that sometimes prevented <code>kubectl portforward</code> to work when TCP and UDP services were configured on the same port (#94728, @amorenoz) [SIG CLI]</p>\n</li>\n<li>\n<p>Fixed bug in reflector that couldn't recover from &quot;Too large resource version&quot; errors with API servers 1.17.0-1.18.5 (#94316, @janeczku) [SIG API Machinery]</p>\n</li>\n<li>\n<p>Fixed bug where kubectl top pod output is not sorted when --sort-by and --containers flags are used together (#93692, @brianpursley) [SIG CLI]</p>\n</li>\n<li>\n<p>Fixed kubelet creating extra sandbox for pods with RestartPolicyOnFailure after all containers succeeded (#92614, @tnqn) [SIG Node and Testing]</p>\n</li>\n<li>\n<p>Fixes a bug where EndpointSlices would not be recreated after rapid Service recreation. (#94730, @robscott) [SIG Apps, Network and Testing]</p>\n</li>\n<li>\n<p>Fixes a race condition in kubelet pod handling (#94751, @auxten) [SIG Node]</p>\n</li>\n<li>\n<p>Fixes an issue proxying to ipv6 pods without specifying a port (#94834, @liggitt) [SIG API Machinery and Network]</p>\n</li>\n<li>\n<p>Ignore root user check when windows pod starts (#92355, @wawa0210) [SIG Node and Windows]</p>\n</li>\n<li>\n<p>Increased maximum IOPS of AWS EBS io1 volumes to 64,000 (current AWS maximum). (#90014, @jacobmarble) [SIG Cloud Provider and Storage]</p>\n</li>\n<li>\n<p>K8s.io/apimachinery: runtime.DefaultUnstructuredConverter.FromUnstructured now handles converting integer fields to typed float values (#93250, @liggitt) [SIG API Machinery]</p>\n</li>\n<li>\n<p>Kube-proxy now trims extra spaces found in loadBalancerSourceRanges to match Service validation. (#94107, @robscott) [SIG Network]</p>\n</li>\n<li>\n<p>Kubeadm now makes sure the etcd manifest is regenerated upon upgrade even when no etcd version change takes place (#94395, @rosti) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Kubeadm: avoid a panic when determining if the running version of CoreDNS is supported during upgrades (#94299, @zouyee) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Kubeadm: ensure &quot;kubeadm reset&quot; does not unmount the root &quot;/var/lib/kubelet&quot; directory if it is mounted by the user (#93702, @thtanaka) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Kubeadm: ensure the etcd data directory is created with 0700 permissions during control-plane init and join (#94102, @neolit123) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Kubeadm: fix the bug that kubeadm tries to call 'docker info' even if the CRI socket was for another CR (#94555, @SataQiu) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Kubeadm: make the kubeconfig files for the kube-controller-manager and kube-scheduler use the LocalAPIEndpoint instead of the ControlPlaneEndpoint. This makes kubeadm clusters more reseliant to version skew problems during immutable upgrades: <a href=\"https://kubernetes.io/docs/setup/release/version-skew-policy/#kube-controller-manager-kube-scheduler-and-cloud-controller-manager\">https://kubernetes.io/docs/setup/release/version-skew-policy/#kube-controller-manager-kube-scheduler-and-cloud-controller-manager</a> (#94398, @neolit123) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Kubeadm: relax the validation of kubeconfig server URLs. Allow the user to define custom kubeconfig server URLs without erroring out during validation of existing kubeconfig files (e.g. when using external CA mode). (#94816, @neolit123) [SIG Cluster Lifecycle]</p>\n</li>\n<li>\n<p>Kubelet: assume that swap is disabled when <code>/proc/swaps</code> does not exist (#93931, @SataQiu) [SIG Node]</p>\n</li>\n<li>\n<p>New Azure instance types do now have correct max data disk count information. (#94340, @ialidzhikov) [SIG Cloud Provider and Storage]</p>\n</li>\n<li>\n<p>Require feature flag CustomCPUCFSQuotaPeriod if setting a non-default cpuCFSQuotaPeriod in kubelet config. (#94687, @karan) [SIG Node]</p>\n</li>\n<li>\n<p>The <code>/debug/api_priority_and_fairness/dump_requests</code> path at an apiserver will no longer return a phantom line for each exempt priority level. (#93406, @MikeSpreitzer) [SIG API Machinery]</p>\n</li>\n<li>\n<p>The kubelet recognizes the --containerd-namespace flag to configure the namespace used by cadvisor. (#87054, @changyaowei) [SIG Node]</p>\n</li>\n<li>\n<p>Update Calico to v3.15.2 (#94241, @lmm) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Update default etcd server version to 3.4.13 (#94287, @jingyih) [SIG API Machinery, Cloud Provider, Cluster Lifecycle and Testing]</p>\n</li>\n<li>\n<p>Use NLB Subnet CIDRs instead of VPC CIDRs in Health Check SG Rules (#93515, @t0rr3sp3dr0) [SIG Cloud Provider]</p>\n</li>\n<li>\n<p>Users will see increase in time for deletion of pods and also guarantee that removal of pod from api server  would mean deletion of all the resources from container runtime. (#92817, @kmala) [SIG Node]</p>\n</li>\n<li>\n<p>Very large patches may now be specified to <code>kubectl patch</code> with the <code>--patch-file</code> flag instead of including them directly on the command line. The <code>--patch</code> and <code>--patch-file</code> flags are mutually exclusive. (#93548, @smarterclayton) [SIG CLI]</p>\n</li>\n</ul>\n<h3>Other (Cleanup or Flake)</h3>\n<ul>\n<li>Adds a bootstrapping ClusterRole, ClusterRoleBinding and group for /metrics, /livez/<em>, /readyz/</em>, &amp; /healthz/* endpoints. (#93311, @logicalhan) [SIG API Machinery, Auth, Cloud Provider and Instrumentation]</li>\n<li>Base-images: Update to debian-iptables:buster-v1.3.0\n<ul>\n<li>Uses iptables 1.8.5</li>\n<li>base-images: Update to debian-base:buster-v1.2.0</li>\n<li>cluster/images/etcd: Build etcd:3.4.13-1 image\n<ul>\n<li>Uses debian-base:buster-v1.2.0 (#94733, @justaugustus) [SIG API Machinery, Release and Testing]</li>\n</ul>\n</li>\n</ul>\n</li>\n<li>Fix kubelet to properly log when a container is started. Before, sometimes the log said that a container is dead and was restarted when it was started for the first time. This only happened when using pods with initContainers and regular containers. (#91469, @rata) [SIG Node]</li>\n<li>Fixes the flooding warning messages about setting volume ownership for configmap/secret volumes (#92878, @jvanz) [SIG Instrumentation, Node and Storage]</li>\n<li>Fixes the message about no auth for metrics in scheduler. (#94035, @zhouya0) [SIG Scheduling]</li>\n<li>Kubeadm: Separate argument key/value in log msg (#94016, @mrueg) [SIG Cluster Lifecycle]</li>\n<li>Kubeadm: remove support for the &quot;ci/k8s-master&quot; version label. This label has been removed in the Kubernetes CI release process and would no longer work in kubeadm. You can use the &quot;ci/latest&quot; version label instead. See kubernetes/test-infra#18517 (#93626, @vikkyomkar) [SIG Cluster Lifecycle]</li>\n<li>Kubeadm: remove the CoreDNS check for known image digests when applying the addon (#94506, @neolit123) [SIG Cluster Lifecycle]</li>\n<li>Lock ExternalPolicyForExternalIP to default, this feature gate will be removed in 1.22. (#94581, @knabben) [SIG Network]</li>\n<li>Service.beta.kubernetes.io/azure-load-balancer-disable-tcp-reset is removed.  All Standard load balancers will always enable tcp resets. (#94297, @MarcPow) [SIG Cloud Provider]</li>\n<li>Stop propagating SelfLink (deprecated in 1.16) in kube-apiserver (#94397, @wojtek-t) [SIG API Machinery and Testing]</li>\n<li>Strip unnecessary security contexts on Windows (#93475, @ravisantoshgudimetla) [SIG Node, Testing and Windows]</li>\n<li>Update CNI plugins to v0.8.7 (#94367, @justaugustus) [SIG Cloud Provider, Network, Node, Release and Testing]</li>\n<li>Update cri-tools to <a href=\\\"https://github.com/kubernetes-sigs/cri-tools/releases/tag/v1.19.0\\\">v1.19.0</a> (#94307, @xmudrii) [SIG Cloud Provider]</li>\n<li>Update etcd client side to v3.4.13 (#94259, @jingyih) [SIG API Machinery and Cloud Provider]</li>\n<li><code>kubectl get ingress</code> now prefers the <code>networking.k8s.io/v1</code> over <code>extensions/v1beta1</code> (deprecated since v1.14). To explicitly request the deprecated version, use <code>kubectl get ingress.v1beta1.extensions</code>. (#94309, @liggitt) [SIG API Machinery and CLI]</li>\n</ul>\n\n  </body>\n</html>"
        	Test:       	TestNewAlpha1Release
--- FAIL: TestNewAlpha1Release (11.65s)
=== RUN   TestNewMinorRelease
Cloning into '/tmp/k8s-test/base-1633481997'...
done.
Checking out files:  38% (8951/23213)   
Checking out files:  39% (9054/23213)   
Checking out files:  40% (9286/23213)   
Checking out files:  41% (9518/23213)   
Checking out files:  42% (9750/23213)   
Checking out files:  43% (9982/23213)   
Checking out files:  44% (10214/23213)   
Checking out files:  45% (10446/23213)   
Checking out files:  46% (10678/23213)   
Checking out files:  47% (10911/23213)   
Checking out files:  48% (11143/23213)   
Checking out files:  49% (11375/23213)   
Checking out files:  50% (11607/23213)   
Checking out files:  51% (11839/23213)   
Checking out files:  52% (12071/23213)   
Checking out files:  53% (12303/23213)   
Checking out files:  54% (12536/23213)   
Checking out files:  55% (12768/23213)   
Checking out files:  56% (13000/23213)   
Checking out files:  57% (13232/23213)   
Checking out files:  58% (13464/23213)   
Checking out files:  59% (13696/23213)   
Checking out files:  60% (13928/23213)   
Checking out files:  61% (14160/23213)   
Checking out files:  62% (14393/23213)   
Checking out files:  63% (14625/23213)   
Checking out files:  64% (14857/23213)   
Checking out files:  65% (15089/23213)   
Checking out files:  66% (15321/23213)   
Checking out files:  67% (15553/23213)   
Checking out files:  68% (15785/23213)   
Checking out files:  69% (16017/23213)   
Checking out files:  70% (16250/23213)   
Checking out files:  71% (16482/23213)   
Checking out files:  72% (16714/23213)   
Checking out files:  73% (16946/23213)   
Checking out files:  74% (17178/23213)   
Checking out files:  75% (17410/23213)   
Checking out files:  76% (17642/23213)   
Checking out files:  77% (17875/23213)   
Checking out files:  78% (18107/23213)   
Checking out files:  79% (18339/23213)   
Checking out files:  80% (18571/23213)   
Checking out files:  81% (18803/23213)   
Checking out files:  82% (19035/23213)   
Checking out files:  83% (19267/23213)   
Checking out files:  84% (19499/23213)   
Checking out files:  85% (19732/23213)   
Checking out files:  86% (19964/23213)   
Checking out files:  87% (20196/23213)   
Checking out files:  88% (20428/23213)   
Checking out files:  89% (20660/23213)   
Checking out files:  89% (20762/23213)   
Checking out files:  90% (20892/23213)   
Checking out files:  91% (21124/23213)   
Checking out files:  92% (21356/23213)   
Checking out files:  93% (21589/23213)   
Checking out files:  94% (21821/23213)   
Checking out files:  95% (22053/23213)   
Checking out files:  96% (22285/23213)   
Checking out files:  97% (22517/23213)   
Checking out files:  98% (22749/23213)   
Checking out files:  99% (22981/23213)   
Checking out files: 100% (23213/23213)   
Checking out files: 100% (23213/23213), done.
Switched to a new branch 'release-2.0'
To /tmp/k8s-test/bare-1633481997
... skipping 27 lines ...
time="2021-10-06T01:00:10Z" level=info msg="Committing changes to main branch in repository"
time="2021-10-06T01:00:10Z" level=info msg="Checking out release-1.21 branch"
time="2021-10-06T01:00:12Z" level=info msg="Removing unnecessary CHANGELOG/CHANGELOG-*.md files"
time="2021-10-06T01:00:12Z" level=info msg="Checking out changelog from main branch"
time="2021-10-06T01:00:12Z" level=info msg="Committing changes to release branch in repository"
    changelog_test.go:46: 
        	Error Trace:	changelog_test.go:46
        	            				changelog_test.go:199
        	Error:      	
        	Test:       	TestNewMinorRelease
--- FAIL: TestNewMinorRelease (20.50s)
=== RUN   TestNewRCRelease
Cloning into '/tmp/k8s-test/base-1633482017'...
done.
Checking out files:  37% (8762/23213)   
Checking out files:  38% (8821/23213)   
Checking out files:  39% (9054/23213)   
Checking out files:  40% (9286/23213)   
Checking out files:  41% (9518/23213)   
Checking out files:  42% (9750/23213)   
Checking out files:  43% (9982/23213)   
Checking out files:  44% (10214/23213)   
Checking out files:  45% (10446/23213)   
Checking out files:  46% (10678/23213)   
Checking out files:  47% (10911/23213)   
Checking out files:  48% (11143/23213)   
Checking out files:  49% (11375/23213)   
Checking out files:  50% (11607/23213)   
Checking out files:  51% (11839/23213)   
Checking out files:  52% (12071/23213)   
Checking out files:  53% (12303/23213)   
Checking out files:  54% (12536/23213)   
Checking out files:  55% (12768/23213)   
Checking out files:  56% (13000/23213)   
Checking out files:  57% (13232/23213)   
Checking out files:  58% (13464/23213)   
Checking out files:  59% (13696/23213)   
Checking out files:  60% (13928/23213)   
Checking out files:  61% (14160/23213)   
Checking out files:  62% (14393/23213)   
Checking out files:  63% (14625/23213)   
Checking out files:  64% (14857/23213)   
Checking out files:  65% (15089/23213)   
Checking out files:  66% (15321/23213)   
Checking out files:  67% (15553/23213)   
Checking out files:  68% (15785/23213)   
Checking out files:  69% (16017/23213)   
Checking out files:  70% (16250/23213)   
Checking out files:  71% (16482/23213)   
Checking out files:  72% (16714/23213)   
Checking out files:  73% (16946/23213)   
Checking out files:  74% (17178/23213)   
Checking out files:  75% (17410/23213)   
Checking out files:  76% (17642/23213)   
Checking out files:  77% (17875/23213)   
Checking out files:  78% (18107/23213)   
Checking out files:  79% (18339/23213)   
Checking out files:  80% (18571/23213)   
Checking out files:  81% (18803/23213)   
Checking out files:  82% (19035/23213)   
Checking out files:  83% (19267/23213)   
Checking out files:  84% (19499/23213)   
Checking out files:  85% (19732/23213)   
Checking out files:  86% (19964/23213)   
Checking out files:  87% (20196/23213)   
Checking out files:  87% (20246/23213)   
Checking out files:  88% (20428/23213)   
Checking out files:  89% (20660/23213)   
Checking out files:  90% (20892/23213)   
Checking out files:  91% (21124/23213)   
Checking out files:  92% (21356/23213)   
Checking out files:  93% (21589/23213)   
Checking out files:  94% (21821/23213)   
Checking out files:  95% (22053/23213)   
Checking out files:  96% (22285/23213)   
Checking out files:  97% (22517/23213)   
Checking out files:  98% (22749/23213)   
Checking out files:  99% (22981/23213)   
Checking out files: 100% (23213/23213)   
Checking out files: 100% (23213/23213), done.
Switched to a new branch 'release-2.0'
To /tmp/k8s-test/bare-1633482017
... skipping 231 lines ...
  stage          Stage a new Kubernetes version
  testgridshot   Take a screenshot of the testgrid dashboards
  version        output version information

Flags:
  -h, --help               help for krel
      --log-level string   the logging verbosity, either 'panic', 'fatal', 'error', 'warning', 'info', 'debug', 'trace' (default "info")
      --nomock             run the command to target the production environment

Use "krel [command] --help" for more information about a command.
--- PASS: TestRootCommand (0.00s)
FAIL
coverage: 10.0% of statements
FAIL	k8s.io/release/cmd/krel/cmd	263.304s
?   	k8s.io/release/cmd/kubepkg	[no test files]
?   	k8s.io/release/cmd/kubepkg/cmd	[no test files]
?   	k8s.io/release/cmd/publish-release	[no test files]
?   	k8s.io/release/cmd/publish-release/cmd	[no test files]
?   	k8s.io/release/cmd/release-notes	[no test files]
?   	k8s.io/release/cmd/schedule-builder	[no test files]
... skipping 275 lines ...
[123-blocking]: https://testgrid.k8s.io/sig-release-1.23-blocking#Summary
[exception requests]: ../EXCEPTIONS.md
[release phases document]: ../release_phases.md

level=info msg="Saving schedule to a file /tmp/schedule-test3566754105/output-1.md."
level=info msg="File saved"
    root_test.go:247: Test case: should fail parsing
level=info msg="Validating schedule-path options..."
level=info msg="Reading the schedule file testdata/bad_schedule.yaml..."
level=info msg="Parsing the schedule..."
    root_test.go:247: Test case: should fail parsing
level=info msg="Validating schedule-path options..."
level=info msg="Reading the schedule file testdata/bad_schedule.yaml..."
level=info msg="Parsing the schedule..."
--- PASS: TestRun (0.00s)
PASS
coverage: 88.9% of statements
ok  	k8s.io/release/cmd/schedule-builder/cmd	0.016s	coverage: 88.9% of statements
?   	k8s.io/release/cmd/vulndash	[no test files]
?   	k8s.io/release/cmd/vulndash/cmd	[no test files]
FAIL
make: *** [Makefile:71: test-go-integration] Error 1