github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-23 19:56:01 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #23893 from mbhinder/kubernetes

Browse Source 
Fixed typo: kuberntes -> kubernetes
This commit is contained in:
Jeff Lowdermilk 2016-04-08 12:47:36 -07:00
commit 7720a16bcf
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
cluster/gce/trusty/master.yaml
View File

@ -57,7 +57,7 @@ script
create_dirs create_dirs
echo "Mount master PD" echo "Mount master PD"
mount_master_pd mount_master_pd
echo "Creating kuberntes master auth file" echo "Creating kubernetes master auth file"
create_master_auth create_master_auth
echo "Creating master instance kubelet auth file" echo "Creating master instance kubelet auth file"
create_master_kubelet_auth create_master_kubelet_auth

2
docs/proposals/release-notes.md
View File

@ -137,7 +137,7 @@ With v1.2.0, the release notes were moved from their previous [github releases](
location to [CHANGELOG.md](../../CHANGELOG.md). Going forward this seems like a good plan. location to [CHANGELOG.md](../../CHANGELOG.md). Going forward this seems like a good plan.
Other projects do similarly. Other projects do similarly.
The kuberntes.tar.gz download link is also displayed along with the release notes The kubernetes.tar.gz download link is also displayed along with the release notes
in [CHANGELOG.md](../../CHANGELOG.md). in [CHANGELOG.md](../../CHANGELOG.md).
Is there any reason to continue publishing anything to github releases if Is there any reason to continue publishing anything to github releases if