Skip to content

Commit 3b3ef25

Browse files
Bradamant3zacharysarah
authored and
zacharysarah
committed
Release 1.10 (#7818)
* Refreshing installation instructions (#7495) * Refreshing installation instructions Added conjure-up. Updated displays and juju versions to current versions. * Updated anchors * Fixed image value version typo (#7768) Was inconsistent with other values * Update flocker reference to the github repo (#7784) * Fix typo in federation document (#7779) * an user -> a user (#7778) * Events are namespaced (#7767) * fix 'monitoring' link lose efficacy problem' (#7764) * docs/concepts/policy/pod-security-policy.md: minor fix. (#7659) * Update downward-api-volume-expose-pod-information.md (#7771) * Update downward-api-volume-expose-pod-information.md The pod spec puts the downward api files into /etc/podinfo, not directly in /etc. Updated docs to reflect this fact. * Update downward-api-volume-expose-pod-information.md One more spot needed fixing. * Update downward-api-volume-expose-pod-information.md Yet another fix, in the container example. * Add Amadeus Case Study (#7783) * Add Amadeus Case Study * add Amadeus logo * Fixed Cyrillic с in 'kube-proxy-cm' (#7787) There was a typo (wrong character) in kube-proxy-cm.yaml - Cyrillic с (UTF-8 0x0441) was used instead of Latin c. * install-kubectl: choose one installation method (#7705) The previous text layout suggested that all installations had to be done, one after another. * Update install-kubeadm.md (#7781) Add note to kubeadm install instruction to help install in other arch i.e. aarch64, ppc64le etc. * repair failure link (#7788) * repair failure link * repair failure link * do change as required * Update k8s201.md (#7777) * Update k8s201.md Change instructions to download yams files directly from the website (as used in other pages.) Added instructions to delete labeled pod to avoid warnings in the subsequent deployment step. * Update k8s201.md Added example of using the exposed host from the a node running Kubernetes. (This works on AWS with Weave; not able to test it on other variations...) * Gramatical fix to kompose introduction (#7792) The original wording didn't through very well. As much of the original sentence has been preserved as possible, primarily to ensure the kompose web address is see both in text and as a href link. * update amadeus.html (#7800) * Fix a missing word in endpoint reconciler section (#7804) * Partners page updates (#7802) * Partners page updates * Update to ZTE link * Make using sysctls a task instead of a concept (#6808) Closes: #4505 * add a note when mount a configmap to pod (#7745) * adjust a note format (#7812) * Update docker-cli-to-kubectl.md (#7748) * Update docker-cli-to-kubectl.md Edited the document for adherence to the style guide and word usage. * Update docker-cli-to-kubectl.md * Incorporated the changes suggested.
1 parent d74ce9b commit 3b3ef25

File tree

4 files changed

+203
-9
lines changed

4 files changed

+203
-9
lines changed

_includes/partner-script.js

+93-9
Original file line numberDiff line numberDiff line change
@@ -1519,7 +1519,7 @@
15191519
type: 1,
15201520
name: 'Kloia',
15211521
logo: 'kloia',
1522-
link: 'https://devops-as-a-service.kloia.com/',
1522+
link: 'https://kloia.com/kubernetes/',
15231523
blurb: 'Kloia is DevOps and Microservices Consultancy company that helps its customers to migrate their environment to cloud platforms for enabling more scalable and secure environments. We use Kubernetes to provide our customers all-in-one solutions in an cloud-agnostic way.'
15241524
},
15251525
{
@@ -1550,13 +1550,6 @@
15501550
link: 'https://www.bloombase.com/go/kubernetes',
15511551
blurb: 'Bloombase provides high bandwidth, defense-in-depth data-at-rest encryption to lock down Kubernetes crown-jewels at scale.'
15521552
},
1553-
{
1554-
type: 0,
1555-
name: 'Kloia',
1556-
logo: 'kloia',
1557-
link: 'https://docs.codefresh.io/docs/codefresh-kubernetes-integration-beta',
1558-
blurb: 'Kloia is DevOps and Microservices Consultancy company that helps its customers to migrate their environment to cloud platforms for enabling more scalable and secure environments. We use Kubernetes to provide our customers all-in-one solutions in an cloud-agnostic way.'
1559-
},
15601553
{
15611554
type: 0,
15621555
name: 'Kasten',
@@ -1620,13 +1613,104 @@
16201613
link: 'http://harmonycloud.cn/products/rongqiyun/',
16211614
blurb: 'Harmonycloud - Harmonycloud Container Platform'
16221615
},
1616+
{
1617+
type: 3,
1618+
name: 'Woqutech',
1619+
logo: 'woqutech',
1620+
link: 'http://www.woqutech.com/product/product-16-247.html#sss',
1621+
blurb: 'Woqutech - QFusion'
1622+
},
1623+
{
1624+
type: 3,
1625+
name: 'Baidu',
1626+
logo: 'baidu',
1627+
link: 'https://cloud.baidu.com/product/cce.html',
1628+
blurb: 'Baidu Cloud - Baidu Cloud Container Engine'
1629+
},
16231630
{
16241631
type: 3,
16251632
name: 'ZTE',
16261633
logo: 'zte',
1627-
link: 'https://sdnfv.zte.com.cn/zh-CN/home',
1634+
link: 'https://sdnfv.zte.com.cn/en/home',
16281635
blurb: 'ZTE - TECS OpenPalette'
16291636
},
1637+
{
1638+
type: 1,
1639+
name: 'Automatic Server AG',
1640+
logo: 'asag',
1641+
link: 'http://www.automatic-server.com/paas.html',
1642+
blurb: 'We install and operate Kubernetes in big enterprises, create deployment workflows and help to migrate.'
1643+
},
1644+
{
1645+
type: 1,
1646+
name: 'Circulo Siete',
1647+
logo: 'circulo',
1648+
link: 'https://circulosiete.com/consultoria/kubernetes/',
1649+
blurb: 'We are a Mexico based company offering training, consulting and support to migrate your workloads to Kubernetes, Cloud Native Microservices & Devops.'
1650+
},
1651+
{
1652+
type: 1,
1653+
name: 'DevOpsGuru',
1654+
logo: 'devopsguru',
1655+
link: 'http://devopsguru.ca/workshop',
1656+
blurb: 'DevOpsGuru work with small business to transform from physical to virtual to containerization.'
1657+
},
1658+
{
1659+
type: 1,
1660+
name: 'EIN Intelligence Co., Ltd',
1661+
logo: 'ein',
1662+
link: 'https://ein.io',
1663+
blurb: 'Startups and agile enterprises in South Korea.'
1664+
},
1665+
{
1666+
type: 0,
1667+
name: 'GuardiCore',
1668+
logo: 'guardicore',
1669+
link: 'https://www.guardicore.com/',
1670+
blurb: 'GuardiCore provided process level visibility and network policy enforcement on containerized assets on the Kubernetes platform.'
1671+
},
1672+
{
1673+
type: 0,
1674+
name: 'Hedvig',
1675+
logo: 'hevig',
1676+
link: 'https://www.hedviginc.com/blog/provisioning-hedvig-storage-with-kubernetes',
1677+
blurb: 'Hedvig is software-defined storage that uses NFS or iSCSI for persistent volumes for provisioning shared storage for pods and containers.'
1678+
},
1679+
{
1680+
type: 0,
1681+
name: 'Hewlett Packard Enterprise',
1682+
logo: 'hpe',
1683+
link: ' https://www.hpe.com/us/en/storage/containers.html',
1684+
blurb: 'Persistent Storage that makes data as easy to manage as containers: dynamic provisioning, policy-based performance & protection, QoS, & more.'
1685+
},
1686+
{
1687+
type: 0,
1688+
name: 'JetBrains',
1689+
logo: 'jetbrains',
1690+
link: 'https://blog.jetbrains.com/teamcity/2017/10/teamcity-kubernetes-support-plugin/',
1691+
blurb: 'Run TeamCity cloud build agents in a Kubernetes cluster. Provides Helm support as a build step.'
1692+
},
1693+
{
1694+
type: 2,
1695+
name: 'Opensense',
1696+
logo: 'opensense',
1697+
link: 'http://www.opensense.fr/en/kubernetes-en/',
1698+
blurb: 'We provide Kubernetes services (integration, operation, training) as well as development of banking microservices based on our extended experience with cloud of containers, microservices, data management and financial sector.'
1699+
},
1700+
{
1701+
type: 2,
1702+
name: 'SAP SE',
1703+
logo: 'sap',
1704+
link: 'https://cloudplatform.sap.com',
1705+
blurb: 'The SAP Cloud Platform provides in-memory capabilities and unique business services for building and extending applications. With open sourced Project Gardener, SAP utilizes the power of Kubernetes to enable an open, robust, multi-cloud experience for our customers. You can use simple, modern cloud native design principles and leverage skills your organization already has to deliver agile and transformative applications, while integrating with the latest SAP Leonardo business features.'
1706+
},
1707+
{
1708+
type: 1,
1709+
name: 'Mobilise Cloud Services Limited',
1710+
logo: 'mobilise',
1711+
link: 'http://www.mobilise.cloud/services/serverless-application-delivery',
1712+
blurb: 'Mobilise helps organisations adopt Kubernetes and integrate with their CI/CD tooling.'
1713+
},
16301714
{
16311715
type: 0,
16321716
>>>>>>> merge master to 1.10, with fixes (#7682)

_redirects

+8
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,15 @@
5959
/docs/admin/resourcequota/limitstorageconsumption/ /docs/tasks/administer-cluster/limit-storage-consumption/ 301
6060
/docs/admin/resourcequota/walkthrough/ /docs/tasks/administer-cluster/quota-api-object/ 301
6161
/docs/admin/static-pods/ /docs/tasks/administer-cluster/static-pod/ 301
62+
<<<<<<< HEAD
63+
/docs/admin/sysctls/ /docs/tasks/administer-cluster/sysctl-cluster/ 301
64+
||||||| merged common ancestors
65+
/docs/admin/sysctls/ /docs/concepts/cluster-administration/sysctl-cluster/ 301
66+
/docs/admin/upgrade-1-6/ /docs/tasks/administer-cluster/upgrade-1-6/ 301
67+
=======
6268
/docs/admin/sysctls/ /docs/tasks/administer-cluster/sysctl-cluster/ 301
69+
/docs/admin/upgrade-1-6/ /docs/tasks/administer-cluster/upgrade-1-6/ 301
70+
>>>>>>> Release 1.10 (#7818)
6371
/docs/admin/resource-quota/ /docs/concepts/policy/resource-quotas/ 301
6472
/docs/admin/upgrade-1-6/ /docs/tasks/administer-cluster/upgrade-downgrade/upgrade-1-6/ 301
6573

docs/reference/kubectl/docker-cli-to-kubectl.md

+54
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,13 @@ You can use the Kubernetes command line tool kubectl to interact with the api. Y
1313

1414
#### docker run
1515

16+
<<<<<<< HEAD
1617
To run an nginx Deployment and expose the Deployment, see [kubectl run](/docs/user-guide/kubectl/{{page.version}}/#run).
18+
||||||| merged common ancestors
19+
How do I run an nginx Deployment and expose it to the world? Checkout [kubectl run](/docs/user-guide/kubectl/{{page.version}}/#run).
20+
=======
21+
To run an nginx Deployment and expose the Deployment, see [kubectl run](/docs/reference/generated/kubectl/kubectl-commands/{{page.version}}/#run).
22+
>>>>>>> Release 1.10 (#7818)
1723
1824
docker:
1925

@@ -59,7 +65,13 @@ To destroy the Deployment and its pods you need to run `kubectl delete deploymen
5965

6066
#### docker ps
6167

68+
<<<<<<< HEAD
6269
To list what is currently running, see [kubectl get](/docs/user-guide/kubectl/{{page.version}}/#get).
70+
||||||| merged common ancestors
71+
How do I list what is currently running? Checkout [kubectl get](/docs/user-guide/kubectl/{{page.version}}/#get).
72+
=======
73+
To list what is currently running, see [kubectl get](/docs/reference/generated/kubectl/kubectl-commands/{{page.version}}/#get).
74+
>>>>>>> Release 1.10 (#7818)
6375
6476
docker:
6577

@@ -81,7 +93,13 @@ ubuntu 0/1 Completed 0 20s
8193

8294
#### docker attach
8395

96+
<<<<<<< HEAD
8497
To attach a process that is already running in a container, see [kubectl attach](/docs/user-guide/kubectl/{{page.version}}/#attach).
98+
||||||| merged common ancestors
99+
How do I attach to a process that is already running in a container? Checkout [kubectl attach](/docs/user-guide/kubectl/{{page.version}}/#attach).
100+
=======
101+
To attach a process that is already running in a container, see [kubectl attach](/docs/reference/generated/kubectl/kubectl-commands/{{page.version}}/#attach).
102+
>>>>>>> Release 1.10 (#7818)
85103
86104
docker:
87105

@@ -109,7 +127,13 @@ To detach from the container, you can type the escape sequence Ctrl+P followed b
109127

110128
#### docker exec
111129

130+
<<<<<<< HEAD
112131
To execute a command in a container, see [kubectl exec](/docs/user-guide/kubectl/{{page.version}}/#exec).
132+
||||||| merged common ancestors
133+
How do I execute a command in a container? Checkout [kubectl exec](/docs/user-guide/kubectl/{{page.version}}/#exec).
134+
=======
135+
To execute a command in a container, see [kubectl exec](/docs/reference/generated/kubectl/kubectl-commands/{{page.version}}/#exec).
136+
>>>>>>> Release 1.10 (#7818)
113137
114138
docker:
115139

@@ -154,7 +178,13 @@ For more information, see [Get a Shell to a Running Container](/docs/tasks/debug
154178

155179
#### docker logs
156180

181+
<<<<<<< HEAD
157182
To follow stdout/stderr of a process that is running, see [kubectl logs](/docs/user-guide/kubectl/{{page.version}}/#logs).
183+
||||||| merged common ancestors
184+
How do I follow stdout/stderr of a running process? Checkout [kubectl logs](/docs/user-guide/kubectl/{{page.version}}/#logs).
185+
=======
186+
To follow stdout/stderr of a process that is running, see [kubectl logs](/docs/reference/generated/kubectl/kubectl-commands/{{page.version}}/#logs).
187+
>>>>>>> Release 1.10 (#7818)
158188
159189

160190
docker:
@@ -181,11 +211,23 @@ $ kubectl logs --previous nginx-app-zibvs
181211
10.240.63.110 - - [14/Jul/2015:01:09:02 +0000] "GET / HTTP/1.1" 200 612 "-" "curl/7.26.0" "-"
182212
```
183213

214+
<<<<<<< HEAD
184215
For more information, see [Logging Architecture](/docs/concepts/cluster-administration/logging/).
216+
||||||| merged common ancestors
217+
See [Logging and Monitoring Cluster Activity](/docs/concepts/cluster-administration/logging/) for more information.
218+
=======
219+
For more information, see [Logging Architecture](docs/concepts/cluster-administration/logging/).
220+
>>>>>>> Release 1.10 (#7818)
185221
186222
#### docker stop and docker rm
187223

224+
<<<<<<< HEAD
188225
To stop and delete a running process, see [kubectl delete](/docs/user-guide/kubectl/{{page.version}}/#delete).
226+
||||||| merged common ancestors
227+
How do I stop and delete a running process? Checkout [kubectl delete](/docs/user-guide/kubectl/{{page.version}}/#delete).
228+
=======
229+
To stop and delete a running process, see [kubectl delete](/docs/reference/generated/kubectl/kubectl-commands/{{page.version}}/#delete).
230+
>>>>>>> Release 1.10 (#7818)
189231
190232
docker:
191233

@@ -228,7 +270,13 @@ There is no direct analog of `docker login` in kubectl. If you are interested in
228270

229271
#### docker version
230272

273+
<<<<<<< HEAD
231274
To get the version of client and server, see [kubectl version](/docs/user-guide/kubectl/{{page.version}}/#version).
275+
||||||| merged common ancestors
276+
How do I get the version of my client and server? Checkout [kubectl version](/docs/user-guide/kubectl/{{page.version}}/#version).
277+
=======
278+
To get the version of client and server, see [kubectl version](/docs/reference/generated/kubectl/kubectl-commands{{page.version}}/#version).
279+
>>>>>>> Release 1.10 (#7818)
232280
233281
docker:
234282

@@ -256,7 +304,13 @@ Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.9+a3d1dfa6f4
256304

257305
#### docker info
258306

307+
<<<<<<< HEAD
259308
To get miscellaneous information about the environment and configuration, see [kubectl cluster-info](/docs/user-guide/kubectl/{{page.version}}/#cluster-info).
309+
||||||| merged common ancestors
310+
How do I get miscellaneous info about my environment and configuration? Checkout [kubectl cluster-info](/docs/user-guide/kubectl/{{page.version}}/#cluster-info).
311+
=======
312+
To get miscellaneous information about the environment and configuration, see [kubectl cluster-info](/docs/reference/generated/kubectl/kubectl-commands/{{page.version}}/#cluster-info).
313+
>>>>>>> Release 1.10 (#7818)
260314
261315
docker:
262316

docs/tasks/administer-cluster/sysctl-cluster.md

+48
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,25 @@
11
---
22
<<<<<<< HEAD:docs/tasks/administer-cluster/sysctl-cluster.md
3+
<<<<<<< HEAD:docs/tasks/administer-cluster/sysctl-cluster.md
34
||||||| merged common ancestors
45
approvers:
56
- sttts
67
=======
8+
||||||| merged common ancestors
9+
=======
10+
title: Using Sysctls in a Kubernetes Cluster
11+
>>>>>>> Release 1.10 (#7818):docs/tasks/administer-cluster/sysctl-cluster.md
712
reviewers:
813
- sttts
14+
<<<<<<< HEAD:docs/tasks/administer-cluster/sysctl-cluster.md
915
>>>>>>> merge master to 1.10, with fixes (#7682):docs/concepts/cluster-administration/sysctl-cluster.md
1016
title: Using Sysctls in a Kubernetes Cluster
1117
reviewers:
1218
- sttts
19+
||||||| merged common ancestors
20+
title: Using Sysctls in a Kubernetes Cluster
21+
=======
22+
>>>>>>> Release 1.10 (#7818):docs/tasks/administer-cluster/sysctl-cluster.md
1323
---
1424

1525
{% capture overview %}
@@ -127,6 +137,7 @@ metadata:
127137
spec:
128138
...
129139
```
140+
<<<<<<< HEAD:docs/tasks/administer-cluster/sysctl-cluster.md
130141
{% endcapture %}
131142
132143
{% capture discussion %}
@@ -135,7 +146,14 @@ spec:
135146
is at-your-own-risk and can lead to severe problems like wrong behavior of
136147
containers, resource shortage or complete breakage of a node.
137148
{: .warning}
149+
||||||| merged common ancestors
150+
=======
151+
{% endcapture %}
138152
153+
{% capture discussion %}
154+
>>>>>>> Release 1.10 (#7818):docs/tasks/administer-cluster/sysctl-cluster.md
155+
156+
<<<<<<< HEAD:docs/tasks/administer-cluster/sysctl-cluster.md
139157
It is good practice to consider nodes with special sysctl settings as
140158
_tainted_ within a cluster, and only schedule pods onto them which need those
141159
sysctl settings. It is suggested to use the Kubernetes [_taints and toleration_
@@ -146,6 +164,28 @@ enabled those two _unsafe_ sysctls explicitly. As with _node-level_ sysctls it
146164
is recommended to use
147165
[_taints and toleration_ feature](/docs/user-guide/kubectl/{{page.version}}/#taint) or
148166
[taints on nodes](/docs/concepts/configuration/taint-and-toleration/)
167+
||||||| merged common ancestors
168+
**Note**: a pod with the _unsafe_ sysctls specified above will fail to launch on
169+
any node which has not enabled those two _unsafe_ sysctls explicitly. As with
170+
_node-level_ sysctls it is recommended to use [_taints and toleration_
171+
feature](/docs/user-guide/kubectl/{{page.version}}/#taint) or [taints on nodes](/docs/concepts/configuration/taint-and-toleration/)
172+
=======
173+
**Warning**: Due to their nature of being _unsafe_, the use of _unsafe_ sysctls
174+
is at-your-own-risk and can lead to severe problems like wrong behavior of
175+
containers, resource shortage or complete breakage of a node.
176+
{: .warning}
177+
178+
It is good practice to consider nodes with special sysctl settings as
179+
_tainted_ within a cluster, and only schedule pods onto them which need those
180+
sysctl settings. It is suggested to use the Kubernetes [_taints and toleration_
181+
feature](/docs/user-guide/kubectl/{{page.version}}/#taint) to implement this.
182+
183+
A pod with the _unsafe_ sysctls will fail to launch on any node which has not
184+
enabled those two _unsafe_ sysctls explicitly. As with _node-level_ sysctls it
185+
is recommended to use
186+
[_taints and toleration_ feature](/docs/user-guide/kubectl/{{page.version}}/#taint) or
187+
[taints on nodes](/docs/concepts/configuration/taint-and-toleration/)
188+
>>>>>>> Release 1.10 (#7818):docs/tasks/administer-cluster/sysctl-cluster.md
149189
to schedule those pods onto the right nodes.
150190
<<<<<<< HEAD:docs/tasks/administer-cluster/sysctl-cluster.md
151191
@@ -169,6 +209,7 @@ metadata:
169209
spec:
170210
...
171211
```
212+
<<<<<<< HEAD:docs/tasks/administer-cluster/sysctl-cluster.md
172213

173214
{% endcapture %}
174215

@@ -195,3 +236,10 @@ spec:
195236
...
196237
```
197238
>>>>>>> merge master to 1.10, with fixes (#7682):docs/concepts/cluster-administration/sysctl-cluster.md
239+
||||||| merged common ancestors
240+
=======
241+
242+
{% endcapture %}
243+
244+
{% include templates/task.md %}
245+
>>>>>>> Release 1.10 (#7818):docs/tasks/administer-cluster/sysctl-cluster.md

0 commit comments

Comments
 (0)