-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OSDOCS-16109# Add docs for tech preview of azure dedicated disk for etcd #99801
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
// Module included in the following assemblies: | ||
// | ||
// * installing/installing_azure/ipi/installing-azure-customizations.adoc | ||
// * installing/installing_azure/ipi/installing-azure-network-customizations.adoc | ||
// * installing/installing_azure/ipi/installing-restricted-networks-azure-installer-provisioned.adoc | ||
|
||
:_mod-docs-content-type: PROCEDURE | ||
[id="installation-azure-dedicated-disks_{context}"] | ||
= Configuring a dedicated disk for etcd | ||
|
||
You can install your {product-title} cluster on {azure-first} with a dedicated data disk for `etcd`. This configuration attaches a separate managed disk to each control plane node and uses it only for `etcd` data, which can improve I/O performance and stability. | ||
|
||
:FeatureName: Dedicated disk for etcd | ||
|
||
include::snippets/technology-preview.adoc[] | ||
|
||
.Prerequisites | ||
* You have created an `install-config.yaml` file. | ||
|
||
.Procedure | ||
|
||
* To configure a dedicated `etcd` disk, edit the `install-config.yaml` file and add the `diskSetup` and `dataDisks` parameters to the `controlPlane` stanza: | ||
+ | ||
[source,yaml] | ||
---- | ||
controlPlane: | ||
architecture: amd64 | ||
hyperthreading: Enabled | ||
name: master | ||
diskSetup: | ||
- type: etcd <1> | ||
etcd: | ||
platformDiskID: "etcddisk" <2> | ||
platform: | ||
azure: | ||
type: Standard_D4s_v5 | ||
dataDisks: | ||
- nameSuffix: etcddisk <3> | ||
diskSizeGB: 20 <4> | ||
lun: 0 <5> | ||
replicas: 3 | ||
---- | ||
|
||
<1> Specify `etcd`. | ||
<2> Specify a name to identify the disk. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The platformDiskID has limitation, it could not be longer than 12 characters. |
||
<3> Specify the same value given for `platformDiskID`. | ||
<4> Specify a disk size in GB. This can be any integer from `8` through `32`. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. hmm, why does disk size have limitation? It works when I set to more than 32. Or anything that I missed? cc @jcpowermac There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I thought it was anything greater than 0, let me double check |
||
+ | ||
[NOTE] | ||
==== | ||
A minimum of 20 GB ensures enough space is available for defragmentation operations. | ||
==== | ||
<5> Specify a logical unit number (LUN). This can be any integer from `0` through `63` that is not used by another disk. |
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In install-config.yaml parameters, dataDisks objects are described under controlPlane machinepool.
Suggest to keep consistent here, something as below:
And parameter cachingType is also missed under dataDisks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my concern with indicating readwrite for cachetype is data loss, maybe a link to azure documentation explaining the risks? for etcd though I would think None is more appropriate
also in researching this I see we have an issue that should be resolved:
https://learn.microsoft.com/en-us/azure/virtual-machines/premium-storage-performance#optimize-performance-on-linux-vms
I will put in a bug to fix this.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jinyunma @jcpowermac If cachingType: None is the safe option and there isn't a specific use case that necessitates the other two options (which also entail significant risks/unclear benefits), I would prefer to make cachingType: None the requirement for this 4.20 version of the documentation due to time constraints, and revisit later.