507 lines
54 KiB
HTML
507 lines
54 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>Kubernetes cluster</title>
|
||
<meta name="generator" content="Help+Manual" />
|
||
<meta name="keywords" content="" />
|
||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
|
||
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
|
||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||
<meta name="description" content="BRIX is installed in a Kubernetes cluster. To manage it, we recommend using the Deckhouse platform built on Open Source components. " />
|
||
<meta name="picture" content="" />
|
||
<meta property="og:type" content="website" />
|
||
<meta property="og:title" content="Full documentation for BRIX365 platform. Low-code developer guide. User guide. Admin guide. Developer guide." />
|
||
<meta property="og:url" content="https://brix365.com/en/help" />
|
||
<meta property="og:image" content="" />
|
||
<link rel="icon" href="favicon.png" type="image/png" />
|
||
|
||
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet" />
|
||
<link rel="stylesheet" href="./jquery-ui.min.css" />
|
||
<link rel="stylesheet" href="default.css" />
|
||
<link rel="stylesheet" href="./search-yandex.css" />
|
||
<link rel="stylesheet" href="./article.css" />
|
||
<link rel="stylesheet" href="./glossary.css" />
|
||
<link rel="stylesheet" href="./theme.css" />
|
||
<script type="text/javascript" src="jquery.js"></script>
|
||
<script type="text/javascript" src="helpman_settings.js"></script>
|
||
<script type="text/javascript" src="helpman_topicinit.js"></script>
|
||
|
||
<script type="text/javascript" src="highlight.js"></script>
|
||
<script type="text/javascript">
|
||
$(document).ready(function(){highlight();});
|
||
</script>
|
||
</head>
|
||
|
||
<body>
|
||
|
||
<script>!function(e,t,c,n,r,a,m){e.ym=e.ym||function(){(e.ym.a=e.ym.a||[]).push(arguments)},e.ym.l=1*new Date;for(var s=0;s<document.scripts.length;s++)if(document.scripts[s].src===n)return;a=t.createElement(c),m=t.getElementsByTagName(c)[0],a.async=1,a.src=n,m.parentNode.insertBefore(a,m)}(window,document,"script","https://mc.yandex.ru/metrika/tag.js"),ym(83179930,"init",{clickmap:!0,trackLinks:!0,accurateTrackBounce:!0,webvisor:!0})</script><noscript><div><img alt=""src=https://mc.yandex.ru/watch/83179930 style=position:absolute;left:-9999px></div></noscript>
|
||
|
||
<header class="header elma-365">
|
||
<div class="container">
|
||
<a class="header__logo" href="https://brix365.com/en/help">
|
||
<img src="./logo-en.svg" alt="header logo">
|
||
</a>
|
||
<!-- <div class="hero__search-form" id="search-panel">
|
||
<form class="search-form" onsubmit="ym(83180416,'reachGoal','poisk')">
|
||
<label class="search-form__label">
|
||
<span id="reset-search" class="search__icon"></span>
|
||
<input class="search-form__input" type="text">
|
||
</label>
|
||
<input class="search-form__submit" type="submit" value="Submit">
|
||
</form>
|
||
</div> -->
|
||
|
||
<div class="hero__search-form" id="search-panel"> <form class="search-form"> <label class="search-form__label"> <span id="reset-search" class="search__icon"></span> <input class="search-form__input" type="text"> </label> <input class="search-form__submit" type="submit" value="Submit"> </form> </div>
|
||
<div class="hero__search">
|
||
<a href="#" id="search-icon" class="hero__search-icon">
|
||
<img src="search-icon-white.svg" alt="search string">
|
||
</a>
|
||
<a href="#" id="side-menu-icon" class="hero__side-icon">
|
||
<img src="side_menu.svg" alt="side menu">
|
||
</a>
|
||
</div>
|
||
<div class="header__navi">
|
||
|
||
<ul class="header__list"><li><span class="solution-select"><span class="solution-select__selected"></span><svg width="7" height="4" viewBox="0 0 7 4" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M1 1L3.5 3.5L6 1" stroke="white" stroke-linecap="round" stroke-linejoin="round"/></svg><ul class="solution-select__list"><li><a class="project-link" href="https://brix365.com/en/help/platform/get-trial.html">Platform</a></li><li><a class="project-link" href="https://brix365.com/en/help/ecm/ecm-functions.html">ECM</a></li><li><a class="project-link" href="https://brix365.com/en/help/crm/crm_overview.html">CRM</a></li><li><a class="project-link" href="https://brix365.com/en/help/service/service-functions.html">Service</a></li><li><a class="project-link" href="https://brix365.com/en/help/projects/projects-functions.html">Projects</a></li><li><a class="project-link" href="https://brix365.com/en/help/business_solutions/-elma365-store.html">Business Solutions</a></li></ul></span></li><li><a href="https://api.brix365.com/en/" target="_blank">API</a></li><li><a href="https://tssdk.brix365.com/" target="_blank">SDK</a></li></ul>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
|
||
</header>
|
||
|
||
|
||
|
||
|
||
<main class="main container">
|
||
|
||
<aside class="sidebar" id="sidebar">
|
||
<div class="sidebar__header">
|
||
<a class="header__logo" href="https://brix365.com/en/help">
|
||
<img src="./logo-light-en.svg">
|
||
</a>
|
||
<span class="sidebar__close elma-365-close" id="close"></span>
|
||
</div>
|
||
<div class="sidebar__wrapper" id="side-menu">
|
||
|
||
</div>
|
||
</aside>
|
||
|
||
<article class="article" id="article">
|
||
<div class="article-inner">
|
||
<div class="content">
|
||
<header class="article__header">
|
||
<div class="article__bread" style="display:flex; gap:10px;">
|
||
<span id="subcategory" class="search-res__item-category search-res__item-category_subcategory subcategory article__badge"></span>
|
||
|
||
<div class="topic__breadcrumbs">
|
||
<p><a href="elma365-on-premises.html">BRIX On-Premises</a> > <a href="infrastructure-preparation.html">Prepare infrastructure</a> > Kubernetes / Kubernetes cluster</p>
|
||
</div>
|
||
|
||
</div>
|
||
<div class="topic__title"><h1 class="p_Heading1"><span class="f_Heading1">Kubernetes cluster</span></h1>
|
||
</div>
|
||
|
||
</header>
|
||
<section class="article__content">
|
||
<div class="scroll-top-inner">
|
||
<a href="#h1-article" class="scroll-top"></a>
|
||
</div>
|
||
<!-- Placeholder for topic body. -->
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><span style="font-family: Inter;">BRIX is installed in a Kubernetes cluster. To manage it, we recommend using the <a href="https://deckhouse.io/" target="_blank" class="weblink">Deckhouse</a> platform built on Open Source components. </span></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><span style="font-family: Inter;">Deckhouse is <a href="https://landscape.cncf.io/?view-mode=card&classify=category&sort-by=name&sort-direction=asc&item=platform--certified-kubernetes-distribution--flant-deckhouse#app-definition-and-development--application-definition-image-build%20" target="_blank" class="weblink">certified by CNCF</a>. Besides Kubernetes, this platform incorporates additional modules for monitoring, traffic balancing, autoscaling, secure access, and more. The modules are pre‑configured, integrated with each other, and ready to use. The management of all cluster components and the platform, as well as their updates, are fully automated.</span></p>
|
||
<p class="p_Normal">You can check the supported Kubernetes versions for the platform in <a href="https://deckhouse.io/products/kubernetes-platform/documentation/v1/supported_versions.html" target="_blank" class="weblink">the official Deckhouse documentation</a>.</p>
|
||
<p class="p_Normal">This article outlines the deployment of a Kubernetes cluster consisting of a single master node.</p>
|
||
<p class="p_Normal">The installation consists of five steps:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal"><a href="kubernetes-deckhouse-air-gap.html#infrastructure-preparation" class="topiclink">Prepare infrastructure</a>.</li><li value="2" class="p_Normal"><a href="kubernetes-deckhouse-air-gap.html#preparation-config-file" class="topiclink">Prepare configuration file</a>.</li><li value="3" class="p_Normal"><a href="kubernetes-deckhouse-air-gap.html#installation" class="topiclink">Install the Kubernetes cluster based on Deckhouse</a>.</li><li value="4" class="p_Normal"><a href="kubernetes-deckhouse-air-gap.html#setting" class="topiclink">Set up Deckhouse</a>.</li><li value="5" class="p_Normal"><a href="kubernetes-deckhouse-air-gap.html#installation-helm" class="topiclink">Install Helm</a>.</li></ol>
|
||
<h2 class="p_Heading2"><a id="infrastructure-preparation" class="hmanchor"></a><span class="f_Heading2">Step 1: Prepare infrastructure</span></h2>
|
||
<p class="p_Normal">To deploy a Kubernetes cluster based on the Deckhouse platform, you will need:</p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="1" class="p_Normal">A personal computer.</li></ol>
|
||
<p class="p_Normal">A computer from which the installation will be carried out. It is only needed to launch the Deckhouse installer and will not be part of the cluster.</p>
|
||
<p class="p_Normal">System requirements:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">OS: Windows 10+, macOS 10.15+, Linux (Ubuntu 18.04+, Fedora 35+).</li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">Installed Docker for running the Deckhouse installer.</li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">Access to a proxying registry or to a private container image storage with Deckhouse container images.</li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">SSH access by key to the node that will be the master node of the future cluster.</li></ul>
|
||
<ol style="list-style-type:upper-roman" start="2">
|
||
<li value="2" class="p_Normal">Master node.</li></ol>
|
||
<p class="p_Normal">A server (physical server or virtual machine) that will be the master node (master node) of the future cluster.</p>
|
||
<p class="p_Normal">During the installation process, the Deckhouse installer, launched on a personal computer, will connect to the master node via SSH, install the necessary packages, configure the Kubernetes control plane, and deploy Deckhouse.</p>
|
||
<p class="p_Normal">System requirements:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">At least 12 CPU cores.</li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">At least 16 GB of RAM.</li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">At least 200 GB of disk space.</li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">A <a href="https://deckhouse.io/documentation/v1/supported_versions.html" target="_blank" class="weblink">supported OS</a>.</li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">Access to a proxying registry or to a private container image storage with Deckhouse container images.</li></ul>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">Начало внимание</span></p>
|
||
<p class="p_Normal">Deckhouse only supports Bearer token authentication scheme in the <span style="font-weight: bold;">registry</span>.</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">Конец внимание</span></p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Access to a proxy server for downloading OS deb/rpm packages (if necessary).</li><li class="p_Normal">SSH access from a personal computer using key.</li><li class="p_Normal">The node should not have container runtime packages installed, such as containerd or Docker.</li></ul>
|
||
<p class="p_Normal"><span style="font-weight: bold;">Important</span>: Installation directly from the master node is currently not supported. The installer in the form of a Docker image cannot be run on the same node where the master node is planned to be deployed, as the node should not have container runtime packages installed, such as containerd or Docker. In the absence of management nodes, install Docker on any other node of the future cluster, run the Docker image of the installer, install Deckhouse, and then remove the Docker image of the installer from the node along with Docker.</p>
|
||
<ol style="list-style-type:upper-roman" start="3">
|
||
<li value="3" class="p_Normal">Downloading Deckhouse images to the local image registry.</li></ol>
|
||
<p class="p_Normal">You can deploy a Kubernetes cluster using Deckhouse in a closed environment without internet access. For this, first download the Deckhouse platform images on a computer with internet access and upload them to the local image registry. Read more in <a href="downloading-images-deckhouse.html" class="topiclink">Download Deckhouse Images</a>.</p>
|
||
<h2 class="p_Heading2"><a id="preparation-config-file" class="hmanchor"></a><span class="f_Heading2">Step 2: Prepare configuration file</span></h2>
|
||
<p class="p_Normal">To install Deckhouse, prepare a YAML configuration file for installation. To obtain the YAML configuration file, use the <a href="https://deckhouse.io/gs/" target="_blank" class="weblink">Getting started</a> service on the Deckhouse website. The service will generate an up-to-date YAML file for the current version of the platform.</p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="1" class="p_Normal">Generate the YAML file using the <a href="https://deckhouse.io/gs/" target="_blank" class="weblink">Getting started</a> service by following these steps:</li></ol>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">Choose the infrastructure: Bare Metal.</li><li value="2" class="p_Normal">Read the installation information.</li><li value="3" class="p_Normal">Specify the template for the cluster<span style="color: #202122;">’</span>s DNS names. In our case it is <span style="font-weight: bold;">%s.example.com</span>.</li><li value="4" class="p_Normal">Save <code><b>config.yml</b></code>.</li></ol>
|
||
<ol style="list-style-type:upper-roman" start="2">
|
||
<li value="2" class="p_Normal">Make the necessary changes in <code><b>config.yml</b></code> by doing the following:</li></ol>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">Set the cluster<span style="color: #202122;">’</span>s pod address space in <span style="font-weight: bold;">podSubnetCIDR</span>.</li><li value="2" class="p_Normal">Set the cluster<span style="color: #202122;">’</span>s Service address space in <span style="font-weight: bold;">serviceSubnetCIDR</span>.</li><li value="3" class="p_Normal">Specify the desired Kubernetes version in <span style="font-weight: bold;">kubernetesVersion</span>.</li><li value="4" class="p_Normal">Check the update channel in <span style="font-weight: bold;">releaseChannel</span> (Stable).</li><li value="5" class="p_Normal">Verify the domain name template in <span style="font-weight: bold;">publicDomainTemplate</span> (<span style="font-weight: bold;">%s.example.com</span>).<br />
|
||
Used to form domains for system applications in the cluster. For example, <span style="font-weight: bold;">Grafana</span> for the template <span style="font-weight: bold;">%s.example.com</span> will be accessible as <span style="font-weight: bold;">grafana.example.com</span>.</li><li value="6" class="p_Normal">Check the operation mode of the cni-flannel module in <span style="font-weight: bold;">podNetworkMode</span>.<br />
|
||
Flannel operation mode, permissible values are <span style="font-weight: bold;">VXLAN</span> (if your servers have L3 connectivity) or <span style="font-weight: bold;">HostGW</span> (for L2 networks).</li><li value="7" class="p_Normal">Specify the local network to be used by cluster nodes in <span style="font-weight: bold;">internalNetworkCIDRs</span>.<br />
|
||
List of internal networks of cluster nodes, for example, <code><b>'192.168.1.0/24'</b></code>, used for communication between Kubernetes components (kube-apiserver, kubelet, etc.).</li></ol>
|
||
<p class="p_Normal">Example of the initial cluster configuration file: <code><b>config.yml</b></code>.</p>
|
||
<p class="p_Normal">For installation via the internet:</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">apiVersion: deckhouse.io/v1</span><br />
|
||
<span class="f_CodeExample">kind: ClusterConfiguration</span><br />
|
||
<span class="f_CodeExample">clusterType: Static</span><br />
|
||
<span class="f_CodeExample">podSubnetCIDR: 10.111.0.0/16</span><br />
|
||
<span class="f_CodeExample">serviceSubnetCIDR: 10.222.0.0/16</span><br />
|
||
<span class="f_CodeExample">kubernetesVersion: "1.26"</span><br />
|
||
<span class="f_CodeExample">clusterDomain: "cluster.local"</span><br />
|
||
<span class="f_CodeExample">---</span><br />
|
||
<span class="f_CodeExample">apiVersion: deckhouse.io/v1</span><br />
|
||
<span class="f_CodeExample">kind: InitConfiguration</span><br />
|
||
<span class="f_CodeExample">deckhouse:</span><br />
|
||
<span class="f_CodeExample"> releaseChannel: Stable</span><br />
|
||
<span class="f_CodeExample"> configOverrides:</span><br />
|
||
<span class="f_CodeExample"> global:</span><br />
|
||
<span class="f_CodeExample"> modules:</span><br />
|
||
<span class="f_CodeExample"> publicDomainTemplate: "%s.example.com"</span><br />
|
||
<span class="f_CodeExample"> cniFlannelEnabled: </span><span class="f_CodeExample" style="font-weight: bold;">true</span><br />
|
||
<span class="f_CodeExample"> cniFlannel:</span><br />
|
||
<span class="f_CodeExample"> podNetworkMode: VXLAN</span><br />
|
||
<span class="f_CodeExample">---</span><br />
|
||
<span class="f_CodeExample">apiVersion: deckhouse.io/v1</span><br />
|
||
<span class="f_CodeExample">kind: StaticClusterConfiguration</span><br />
|
||
<span class="f_CodeExample">internalNetworkCIDRs:</span><br />
|
||
<span class="f_CodeExample"> - 192.168.1.0/24</span></p>
|
||
<p class="p_Normal"><span style="font-weight: bold;"><a class="dropdown-toggle" style="font-style: normal; font-weight: bold; color: #000000; background-color: transparent; text-decoration: none;" href="javascript:HMToggle('toggle','TOGGLE0186A1')">For offline installation without internet access</a></span></p>
|
||
<div id="TOGGLE0186A1" class="dropdown-toggle-body" style="text-align: left; text-indent: 0; line-height: 1.80; padding: 0 0 0 0; margin: 0 0 0 0;"><table style="border:none; border-spacing:0;">
|
||
<tr>
|
||
<td style="vertical-align:top; padding:0; border:none"><p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">Начало внимание</span></p>
|
||
<p class="p_Normal">To generate the YAML file using the <a href="https://deckhouse.io/gs/" target="_blank" class="weblink">Getting started</a> service, choose the <span style="font-weight: bold;">Private environment</span> infrastructure.</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">Конец внимание</span></p>
|
||
<p class="p_Normal">Set the following parameters in the <span style="font-weight: bold;">InitConfiguration</span> resource:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal"><span style="font-weight: bold;">devBranch</span>: If there are no images in the isolated private repository containing update channel information, use the exact Deckhouse image tag to install Deckhouse Platform. For example, if you want to install release v1.46.3, use the image <code><b>registry.example.com/images/deckhouse/install:v1.46.3</b></code>. Also, specify <code><b>devBranch: v1.46.3</b></code> instead of <code><b>releaseChannel: XXX</b></code>.</li></ul>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal"><span style="font-weight: bold;">imagesRepo</span>: <code><b><PROXY_REGISTRY>/<DECKHOUSE_REPO_PATH>/<DECKHOUSE_REVISION></b></code> — he address of the Deckhouse image in the private repository, considering the edition used. In this article, the images were uploaded to <code><b>registry.example.com/images/deckhouse</b></code>. Read more in <a href="downloading-images-deckhouse.html" class="topiclink">Download Deckhouse Images</a>.</li></ul>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal"><span style="font-weight: bold;">registryDockerCfg</span>: <code><b><BASE64></b></code> — access rights to the private repository, encrypted in Base64. Examples of filling in <span style="font-weight: bold;">registryDockerCfg</span> can be found in the official <a href="https://deckhouse.io/documentation/v1/deckhouse-faq.html" target="_blank" class="weblink">Deckhouse Kubernetes Platform documentation</a>. In this article, anonymous access to Deckhouse images in an external registry is allowed. Generate <span style="font-weight: bold;">registryDockerCfg</span> by executing the following command:</li></ul>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample">echo -n "{\"auths\": { \"registry.example.com:443/images/deckhouse\": {}}}" | base64</span></p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal"><span style="font-weight: bold;">registryScheme</span>: specify the protocol (HTTP or HTTPS) used by the private repository.</li></ul>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal"><span style="font-weight: bold;">registryCA</span>: oot SSL certificate that can verify the SSL certificate of the private registry, for example, if the storage uses a self-signed certificate. If you are using a non-self-signed certificate or the storage works via the HTTP protocol, remove this parameter.</li></ul>
|
||
<p class="p_Normal">Example of the initial cluster configuration file, <code><b>config.yml</b></code>:</p>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample">apiVersion: deckhouse.io/v1</span><br />
|
||
<span class="f_CodeExample">kind: ClusterConfiguration</span><br />
|
||
<span class="f_CodeExample">clusterType: Static</span><br />
|
||
<span class="f_CodeExample">podSubnetCIDR: 10.111.0.0/16</span><br />
|
||
<span class="f_CodeExample">serviceSubnetCIDR: 10.222.0.0/16</span><br />
|
||
<span class="f_CodeExample">kubernetesVersion: "1.23"</span><br />
|
||
<span class="f_CodeExample">clusterDomain: "cluster.local"</span><br />
|
||
<span class="f_CodeExample">---</span><br />
|
||
<span class="f_CodeExample">apiVersion: deckhouse.io/v1</span><br />
|
||
<span class="f_CodeExample">kind: InitConfiguration</span><br />
|
||
<span class="f_CodeExample">deckhouse:</span><br />
|
||
<span class="f_CodeExample"> devBranch: v1.46.3</span><br />
|
||
<span class="f_CodeExample"> configOverrides:</span><br />
|
||
<span class="f_CodeExample"> global:</span><br />
|
||
<span class="f_CodeExample"> modules:</span><br />
|
||
<span class="f_CodeExample"> publicDomainTemplate: "%s.example.com"</span><br />
|
||
<span class="f_CodeExample"> cniFlannelEnabled: </span><span class="f_CodeExample" style="font-weight: bold;">true</span><br />
|
||
<span class="f_CodeExample"> cniFlannel:</span><br />
|
||
<span class="f_CodeExample"> podNetworkMode: VXLAN</span><br />
|
||
<span class="f_CodeExample"> imagesRepo: registry.example.com:443/images/deckhouse</span><br />
|
||
<span class="f_CodeExample"> registryDockerCfg: eyJhdXRocyI6IHsgInJlZ2lzdHJ5LmV4YW1wbGUuY29tOjQ0My9pbWFnZXMvZGVja2hvdXNlIjoge319fQ==</span><br />
|
||
<span class="f_CodeExample"> registryScheme: HTTPS</span><br />
|
||
<span class="f_CodeExample"> registryCA: |</span><br />
|
||
<span class="f_CodeExample"> -----BEGIN CERTIFICATE-----</span><br />
|
||
<span class="f_CodeExample"> MIIFBzCCGu+gAwIBAgIUBZ37mm02QGGcmd5pZvWwnpCfQUowDQYGKoZIhvcNAQEL</span><br />
|
||
<span class="f_CodeExample"> BQAwHjEcMBoGA1UEAwwTaW1hZ2VzLnByb2FjdG9yLnBybzAeFw0yMjA5MjkxNDUw</span><br />
|
||
<span class="f_CodeExample"> ...</span><br />
|
||
<span class="f_CodeExample"> 9UpckrwxPhctmln5/Awd/2gcaRAxI3qBL7SyDFT0YpnGcAiGPY4Z67HhZ7h6y+2F</span><br />
|
||
<span class="f_CodeExample"> fQDSXli0r61/Fenkh5OLMihLYTm+5gjZlG1LCXpaGIpjAf16Q+3/pIqapQ==</span><br />
|
||
<span class="f_CodeExample"> -----END CERTIFICATE-----</span><br />
|
||
<span class="f_CodeExample">---</span><br />
|
||
<span class="f_CodeExample">apiVersion: deckhouse.io/v1</span><br />
|
||
<span class="f_CodeExample">kind: StaticClusterConfiguration</span><br />
|
||
<span class="f_CodeExample">internalNetworkCIDRs:</span><br />
|
||
<span class="f_CodeExample"> - 192.168.1.0/24</span></p>
|
||
</td>
|
||
</tr>
|
||
</table>
|
||
</div>
|
||
<h2 class="p_Heading2"><a id="installation" class="hmanchor"></a><span class="f_Heading2">Step 3: Install the Kubernetes cluster based on Deckhouse</span></h2>
|
||
<p class="p_Normal">The installation of Deckhouse Platform Community Edition involves setting up a cluster (using a Docker-image-based installer) consisting of a single master node. The Deckhouse installer is available as a container image, which requires the configuration files and SSH keys for accessing the master node. It is assumed that the SSH key used is <code><b>~/.ssh/id_rsa</b></code>. The installer is based on the <a href="https://github.com/deckhouse/deckhouse/tree/main/dhctl/" target="_blank" class="weblink">dhctl</a> utility.</p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="1" class="p_Normal">Start the installer.</li></ol>
|
||
<p class="p_Normal"><span style="font-weight: bold;">Important</span>: Direct installation from the master node is currently not supported. The installer, in the form of a Docker image, cannot be run on the same node where the master node deployment is planned, as container runtime packages like containerd or docker should not be installed on the node.</p>
|
||
<p class="p_Normal">The installer is run on a personal computer prepared in the <a href="kubernetes-deckhouse-air-gap.html#infrastructure-preparation" class="topiclink">infrastructure preparation</a> step. On the PC, navigate to the directory with the configuration file <code><b>config.yml</b></code>, prepared during the <a href="kubernetes-deckhouse-air-gap.html#preparation-config-file" class="topiclink">configuration file preparation</a> step.</p>
|
||
<p class="p_Normal">To launch the installer via the internet:</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">sudo docker run --pull=always -it -v "$PWD/config.yml:/config.yml" -v "$HOME/.ssh/:/tmp/.ssh/" registry.deckhouse.io/deckhouse/ce/install:stable bash</span></p>
|
||
<p class="p_Normal"><span style="font-weight: bold;"><a class="dropdown-toggle" style="font-style: normal; font-weight: bold; color: #000000; background-color: transparent; text-decoration: none;" href="javascript:HMToggle('toggle','TOGGLE0186A2')">For offline installation without internet access</a></span></p>
|
||
<div id="TOGGLE0186A2" class="dropdown-toggle-body" style="text-align: left; text-indent: 0; line-height: 1.80; padding: 0 0 0 0; margin: 0 0 0 0;"><table style="border:none; border-spacing:0;">
|
||
<tr>
|
||
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal"> <br />
|
||
Execute the command:</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">sudo docker run --pull=always -it -v "$PWD/config.yml:/config.yml" -v "$HOME/.ssh/:/tmp/.ssh/" example.com:443/images/deckhouse/install:v1.46.3 bash</span></p>
|
||
<p class="p_Normal">where:</p>
|
||
<p class="p_Normal"><code><b>example.com:443/images/deckhouse/install:v1.46.3</b></code> is the version of the release being installed.</p>
|
||
</td>
|
||
</tr>
|
||
</table>
|
||
</div>
|
||
<ol style="list-style-type:upper-roman" start="2">
|
||
<li value="2" class="p_Normal"><a id="install-deckhouse" class="hmanchor"></a>Install Deckhouse. To do this, execute the command inside the installer container:</li></ol>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">dhctl bootstrap --ssh-user=<username> --ssh-host=<master_ip> --ssh-agent-</span><span class="f_CodeExample" style="font-weight: bold;">private</span><span class="f_CodeExample">-keys=/tmp/.ssh/id_rsa \</span><br />
|
||
<span class="f_CodeExample">--config=/config.yml \</span><br />
|
||
<span class="f_CodeExample">--ask-become-pass</span></p>
|
||
<p class="p_Normal">where:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_CodeExample" style="white-space: normal; page-break-inside: auto;"><code><b><username></b></code>.<span style="font-family: 'Courier New',Courier,monospace;"> </span>In the<span class="f_CodeExample"> <code><b>--ssh-user</b></code></span> parameter specify the name of the user who generated the SSH key for installation.</li><li class="p_CodeExample" style="white-space: normal; page-break-inside: auto;"><code><b><master_ip></b></code><span class="f_CodeExample">. </span>This is the IP address of the master node prepared during the <a href="kubernetes-deckhouse-air-gap.html#infrastructure-preparation" class="topiclink">infrastructure preparation</a> step.</li></ul>
|
||
<p class="p_Normal">The installation process may take 15-30 minutes with a good connection.</p>
|
||
<p class="p_Normal"><a class="dropdown-toggle" style="font-style: normal; font-weight: normal; color: #000000; background-color: transparent; text-decoration: none;" href="javascript:HMToggle('toggle','TOGGLE0186A3')">Possible errors when installing Deckhouse</a></p>
|
||
<div id="TOGGLE0186A3" class="dropdown-toggle-body" style="text-align: left; text-indent: 0; line-height: 1.80; padding: 0 0 0 0; margin: 0 0 0 0;"><table style="border:none; border-spacing:0;">
|
||
<tr>
|
||
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal"> <br />
|
||
Errors may occur during Deckhouse installation. Let's see how to resolve them. </p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal"><span style="font-weight: bold;">Port access error</span> — <code><b>Checking required ports availability FAILED</b></code>.</li></ol>
|
||
<p class="p_Normal">To resolve this error, follow the steps below:</p>
|
||
<ol style="list-style-type:lower-latin">
|
||
<li value="1" class="p_Normal">Verify that access to all ports specified in <a href="https://deckhouse.io/products/kubernetes-platform/documentation/v1/network_security_setup.html" target="_blank" class="weblink">the official Deckhouse documentation</a> is configured correctly.</li><li value="2" class="p_Normal">Start the installer again and <a href="kubernetes-deckhouse-air-gap.html#install-deckhouse" class="topiclink">execute the Deckhouse installation command</a>.</li><li value="3" class="p_Normal">Wait for the Deckhouse installation to complete.</li><li value="4" class="p_Normal">If the error occurs again, start the installer and execute the Deckhouse installation command with the <code><b>--preflight-skip-availability-ports-check</b></code> flag. <br />
|
||
Example:</li></ol>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample">dhctl bootstrap --ssh-user=<username> --ssh-host=<master_ip> --ssh-agent-private-keys=/tmp/.ssh/id_rsa --preflight-skip-availability-ports-check \.</span><br />
|
||
<span class="f_CodeExample"> --config=/config.yml.</span><br />
|
||
<span class="f_CodeExample"> --ask-become-pass</span></p>
|
||
<ol style="list-style-type:decimal" start="2">
|
||
<li value="2" class="p_Normal"><span style="font-weight: bold;">Error with access permissions for the user who started the installation (</span><code><b>ssh-user</b></code><span style="font-weight: bold;">) </span>— <code><b>Checking sudo is allowed for user FAILED</b></code>.</li></ol>
|
||
<p class="p_Normal">To resolve it, follow the steps below:</p>
|
||
<ol style="list-style-type:lower-latin">
|
||
<li value="1" class="p_Normal">In the <code><b>/etc/sudoers</b></code> file, verify that the user has sudo permissions on the host where Deckhouse is installed. To grant the rights, add:</li></ol>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample"><user_name> ALL=(ALL) ALL</span> </p>
|
||
<p class="p_Normal"> <br />
|
||
The <code><b><user_name></b></code> records the account of the user who runs the installation.</p>
|
||
<ol style="list-style-type:lower-latin" start="2">
|
||
<li value="2" class="p_Normal">Start the installer again and execute the Deckhouse installation command.</li><li value="3" class="p_Normal">Wait for the Deckhouse installation to complete.</li><li value="4" class="p_Normal">If the error occurs again, start the installer and execute the Deckhouse installation command with the <code><b>--preflight-skip-sudo-allowed</b></code> flag.<br />
|
||
Example:</li></ol>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample">dhctl bootstrap --ssh-user=<username> --ssh-host=<master_ip> --ssh-agent-private-keys=/tmp/.ssh/id_rsa --preflight-skip-sudo-allowed \</span><br />
|
||
<span class="f_CodeExample">--config=/config.yml.</span><br />
|
||
<span class="f_CodeExample">--ask-become-pass</span></p>
|
||
<ol style="list-style-type:decimal" start="3">
|
||
<li value="3" class="p_Normal"><span style="font-weight: bold;">Error when re-running the install script</span> — <code><b>Deckhouse Error: bundle 'bashible' error: execute bundle: exit status 1</b></code>.</li></ol>
|
||
<p class="p_Normal">The error occurs if files from an incomplete Deckhouse installation are left on the master node. To delete the files, run the command on the master node:</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">sudo bash /var/lib/bashible/cleanup_static_node.sh --yes-i-am-sane-and-i-understand-what-i-am-doing</span></p>
|
||
</td>
|
||
</tr>
|
||
</table>
|
||
</div>
|
||
<h2 class="p_Heading2"><a id="setting" class="hmanchor"></a><span class="f_Heading2">Step 4: Set up Deckhouse</span></h2>
|
||
<p class="p_Normal">Connect via SSH to the master node prepared during the <a href="kubernetes-deckhouse-air-gap.html#infrastructure-preparation" class="topiclink">infrastructure preparation</a> step. Perform the following steps:</p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="1" class="p_Heading3">Remove taint restrictions from the master node.</li></ol>
|
||
<p class="p_Normal">In this article, the Kubernetes cluster based on Deckhouse consists of a single node. Allow Deckhouse components to work on the master node. To do this, execute one of the following commands:</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">sudo kubectl patch nodegroup master --type json -p '[{"op": "remove", "path": "/spec/nodeTemplate/taints"}]'</span></p>
|
||
<p class="p_Normal">or</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">sudo -i d8 k patch nodegroup master --type json -p '[{"op": "remove", "path": "/spec/nodeTemplate/taints"}]'</span></p>
|
||
<ol style="list-style-type:upper-roman" start="2">
|
||
<li value="2" class="p_Heading3">Increase the number of pods on the master node.</li></ol>
|
||
<p class="p_Normal">Increase the maximum number of pods on the NodeGroup master nodes by executing one of the following commands:</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">sudo kubectl patch nodegroup master --type=merge -p '{"spec":{"kubelet":{"maxPods":200}}}'</span></p>
|
||
<p class="p_Normal">or</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">sudo -i d8 k patch nodegroup master --type=merge -p '{"spec":{"kubelet":{"maxPods":200}}}'</span></p>
|
||
<ol style="list-style-type:upper-roman" start="3">
|
||
<li value="3" class="p_Normal">Add Local Path Provisioner.</li></ol>
|
||
<p class="p_Normal">By default, storageclass is absent in Deckhouse. Create a custom resource <span style="font-weight: bold;">LocalPathProvisioner</span>, allowing Kubernetes users to use local storage on nodes. Perform the following actions:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">Create a <code><b>local-path-provisioner.yaml</b></code> file on the master node containing the configuration for <span style="font-weight: bold;">LocalPathProvisioner</span>.</li></ol>
|
||
<ol style="list-style-type:decimal" start="2">
|
||
<li value="2" class="p_Normal">Set the desired Reclaim policy (Retain by default). In this article, the parameter <code><b>reclaimPolicy</b></code> is set to <code><b>"Delete"</b></code> (PVs are deleted after PVCs are deleted).</li></ol>
|
||
<p class="p_Normal">Example of a <code><b>local-path-provisioner.yaml</b></code> file:</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">apiVersion: deckhouse.io/v1alpha1</span><br />
|
||
<span class="f_CodeExample">kind: LocalPathProvisioner</span><br />
|
||
<span class="f_CodeExample">metadata:</span><br />
|
||
<span class="f_CodeExample"> name: localpath-deckhouse-system</span><br />
|
||
<span class="f_CodeExample">spec:</span><br />
|
||
<span class="f_CodeExample"> nodeGroups:</span><br />
|
||
<span class="f_CodeExample"> - master</span><br />
|
||
<span class="f_CodeExample"> path: "/opt/local-path-provisioner"</span><br />
|
||
<span class="f_CodeExample"> reclaimPolicy: Delete</span></p>
|
||
<ol style="list-style-type:decimal" start="3">
|
||
<li value="3" class="p_Normal">Apply the <code><b>local-path-provisioner.yaml</b></code> file in Kubernetes by executing the command:</li></ol>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">sudo kubectl apply -f local-path-provisioner.yaml</span></p>
|
||
<ol style="list-style-type:decimal" start="4">
|
||
<li value="4" class="p_CodeExample" style="white-space: normal; page-break-inside: auto;">Set the created <span style="font-weight: bold;">LocalPathProvisioner</span> as the default storageclass (default-class) by executing one of the following commands:</li></ol>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">sudo kubectl patch storageclass localpath-deckhouse-system -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'</span></p>
|
||
<p class="p_Normal">or</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">sudo -i d8 k patch mc global --type merge -p '{"spec": {"settings":{"defaultClusterStorageClass":"localpath-deckhouse-system"}}}'</span></p>
|
||
<ol style="list-style-type:upper-roman" start="4">
|
||
<li value="4" class="p_Normal">Add Ingress Nginx Controller.</li></ol>
|
||
<p class="p_Normal">Deckhouse installs and manages the NGINX Ingress Controller using Custom Resources. If there is more than one node for deploying the Ingress controller, it is installed in a fail-safe mode and takes into account all the features of cloud and bare metal infrastructure implementations, as well as different types of Kubernetes clusters.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">Create an <code><b>ingress-nginx-controller.yml</b></code> file on the master node containing the Ingress controller configuration by executing the following command:</li></ol>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample"># section describing the parameters of the nginx ingress controller</span><br />
|
||
<span class="f_CodeExample"># used version of the Deckhouse API</span><br />
|
||
<span class="f_CodeExample">apiVersion: deckhouse.io/v1</span><br />
|
||
<span class="f_CodeExample">kind: IngressNginxController</span><br />
|
||
<span class="f_CodeExample">metadata:</span><br />
|
||
<span class="f_CodeExample"> name: nginx</span><br />
|
||
<span class="f_CodeExample">spec:</span><br />
|
||
<span class="f_CodeExample"> # name of the Ingress class for serving Ingress NGINX</span><br />
|
||
<span class="f_CodeExample"> ingressClass: nginx</span><br />
|
||
<span class="f_CodeExample"> # how traffic enters from the external world</span><br />
|
||
<span class="f_CodeExample"> inlet: HostPort</span><br />
|
||
<span class="f_CodeExample"> hostPort:</span><br />
|
||
<span class="f_CodeExample"> httpPort: 80</span><br />
|
||
<span class="f_CodeExample"> httpsPort: 443</span><br />
|
||
<span class="f_CodeExample"> # describes which nodes the component will be located on</span><br />
|
||
<span class="f_CodeExample"> # you might want to change</span><br />
|
||
<span class="f_CodeExample"> nodeSelector:</span><br />
|
||
<span class="f_CodeExample"> node-role.kubernetes.io/control-plane: ""</span><br />
|
||
<span class="f_CodeExample"> tolerations:</span><br />
|
||
<span class="f_CodeExample"> </span><span class="f_CodeExample">- effect: NoSchedule</span><br />
|
||
<span class="f_CodeExample"> key: node-role.kubernetes.io/control-plane</span><br />
|
||
<span class="f_CodeExample">- operator: Exists</span></p>
|
||
<ol style="list-style-type:decimal" start="2">
|
||
<li value="2" class="p_CodeExample" style="white-space: normal; page-break-inside: auto;">Apply the <code><b>ingress-nginx-controller.yml</b></code> file in Kubernetes by executing the command:</li></ol>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">sudo kubectl create -f ingress-nginx-controller.yml</span></p>
|
||
<ol style="list-style-type:upper-roman" start="5">
|
||
<li value="5" class="p_Normal">Add a user for access to the cluster web interface.</li></ol>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">Add the <code><b>user.yml</b></code> file on the master node containing the description of the user account and access rights:</li></ol>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample">apiVersion: deckhouse.io/v1</span><br />
|
||
<span class="f_CodeExample">kind: ClusterAuthorizationRule</span><br />
|
||
<span class="f_CodeExample">metadata:</span><br />
|
||
<span class="f_CodeExample"> name: admin</span><br />
|
||
<span class="f_CodeExample">spec:</span><br />
|
||
<span class="f_CodeExample"> # list of Kubernetes RBAC accounts</span><br />
|
||
<span class="f_CodeExample"> subjects:</span><br />
|
||
<span class="f_CodeExample"> - kind: User</span><br />
|
||
<span class="f_CodeExample"> name: admin@deckhouse.io</span><br />
|
||
<span class="f_CodeExample"> # predefined access level template</span><br />
|
||
<span class="f_CodeExample"> accessLevel: SuperAdmin</span><br />
|
||
<span class="f_CodeExample"> # allow the user to do kubectl port-forward</span><br />
|
||
<span class="f_CodeExample"> portForwarding: </span><span class="f_CodeExample" style="font-weight: bold;">true</span><br />
|
||
<span class="f_CodeExample">---</span><br />
|
||
<span class="f_CodeExample"># section describing the parameters of the static user</span><br />
|
||
<span class="f_CodeExample"># used version of the Deckhouse API</span><br />
|
||
<span class="f_CodeExample">apiVersion: deckhouse.io/v1</span><br />
|
||
<span class="f_CodeExample">kind: User</span><br />
|
||
<span class="f_CodeExample">metadata:</span><br />
|
||
<span class="f_CodeExample"> name: admin</span><br />
|
||
<span class="f_CodeExample">spec:</span><br />
|
||
<span class="f_CodeExample"> # user's email</span><br />
|
||
<span class="f_CodeExample"> email: admin@deckhouse.io</span><br />
|
||
<span class="f_CodeExample"> # this is the hash of the password xgnv5gkggd, generated now</span><br />
|
||
<span class="f_CodeExample"> # generate your own or use this one, but only for testing</span><br />
|
||
<span class="f_CodeExample"> # echo "xgnv5gkggd" | htpasswd -BinC 10 "" | cut -d: -f2</span><br />
|
||
<span class="f_CodeExample"> # you might want to change</span><br />
|
||
<span class="f_CodeExample"> password: '$2a$10$4j4cUeyonCfX7aDJyqSHXuAxycsf/sDK0T4n9ySQ7.owE34L1uXTm'</span></p>
|
||
<ol style="list-style-type:decimal" start="2">
|
||
<li value="2" class="p_CodeExample" style="white-space: normal; page-break-inside: auto;">Apply the <code><b>user.yml</b></code> file by executing the following command on the master node:</li></ol>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">sudo kubectl create -f user.yml</span></p>
|
||
<ol style="list-style-type:upper-roman" start="5">
|
||
<li value="6" class="p_Normal">Allow reassigning privilege policy for the running pods:</li></ol>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">sudo kubectl label namespace elma365 security.deckhouse.io/pod-policy=privileged --overwrite</span></p>
|
||
<h2 class="p_Heading2"><a id="installation-helm" class="hmanchor"></a><span class="f_Heading2">Step 5: Install Helm</span></h2>
|
||
<p class="p_Normal">You can install HELM by downloading a specific version manually or by using a script. Both methods are described in detail in <a href="https://helm.sh/docs/intro/install/" target="_blank" class="weblink">the official documentation of the HELM package manager</a>. </p>
|
||
<p class="p_Normal">To download and install the tool manually, do the following:</p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="1" class="p_Normal">To install Helm, visit the <a href="https://github.com/helm/helm/releases" target="_blank" class="weblink">Helm</a> releases page and download the <code><b>helm-vX.Y.Z-linux-amd64.tar.gz</b></code> archive of the required version.</li></ol>
|
||
<p class="p_Normal">For installation via the internet:</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">wget https://get.helm.sh/helm-vX.Y.Z-linux-amd64.tar.gz</span></p>
|
||
<p class="p_Normal"><span style="font-weight: bold;"><a class="dropdown-toggle" style="font-style: normal; font-weight: bold; color: #000000; background-color: transparent; text-decoration: none;" href="javascript:HMToggle('toggle','TOGGLE0186A4')">For offline installation without internet access</a></span></p>
|
||
<div id="TOGGLE0186A4" class="dropdown-toggle-body" style="text-align: left; text-indent: 0; line-height: 1.80; padding: 0 0 0 0; margin: 0 0 0 0;"><table style="border:none; border-spacing:0;">
|
||
<tr>
|
||
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal"> <br />
|
||
On a computer with internet access, go to the Helm releases page and download the <code><b>helm-vX.Y.Z-linux-amd64.tar.gz</b></code> archive of the desired version by executing the command:</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">wget https://get.helm.sh/helm-vX.Y.Z-linux-amd64.tar.gz</span></p>
|
||
<p class="p_Normal">Copy the downloaded archive to the master node.</p>
|
||
</td>
|
||
</tr>
|
||
</table>
|
||
</div>
|
||
<ol style="list-style-type:upper-roman" start="2">
|
||
<li value="2" class="p_Normal">Unpack the archive and move the helm binary file:</li></ol>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">tar -zxvf helm-vX.Y.Z-linux-amd64.tar.gz</span><br />
|
||
<span class="f_CodeExample">mv linux-amd64/helm /usr/local/bin/helm</span></p>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="infrastructure-preparation.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">infrastructure-preparation.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="fail-safe-kubernetes-cluster.html">
|
||
<span class="bottom-nav__link">fail-safe-kubernetes-cluster.html</span> <span
|
||
class="bottom-nav__arrow bottom-nav__arrow--next"></span>
|
||
</a>
|
||
|
||
</div>
|
||
<!-- добавляет на страницу строку блок Была ли статья полезной? -->
|
||
<div class="feedback" id="feedback"><div class="feedback-help"><span><b>Was this helpful?</b></span><form action="" method="POST" class="feedback-form" id="feedback-form"><div class="feedback__popup feedback__popup-response" id="feedback__popup_thx" style="display: none;">Thanks for your feedback!</div><div class="feedback__popup" id="feedback__popup_why" style="display: none;"><div class="feedback__popup-header">Please specify why:</div><input type="radio" name="category" id="bad_recommendation" value="bad_recommendation"><label for="bad_recommendation">Recommendations did not help me</label><input type="radio" name="category" id="difficult_text" value="difficult_text"><label for="difficult_text">Article is hard to understand</label><input type="radio" name="category" id="no_answer" value="no_answer"><label for="no_answer">Didn`t answer my question</label><input type="radio" name="category" id="bad_header" value="bad_header"><label for="bad_header">Content does not match the topic</label><input type="radio" name="category" id="other_reason" value="other_reason"><label for="other_reason">Other</label></div><div class="feedback__popup" id="feedback__popup-other" style="display: none;"><div class="feedback__popup-header">How we can improve it?</div><textarea class="feedback__textarea" name="other" id=""></textarea><input type="submit" class="feedback__other-btn" value="Submit"></div><div class="feedback-form__btn-group"><input type="radio" name="useful" id="feedback__useful_yes" value="true"><label for="feedback__useful_yes"><img src="like.svg" class="small-img" alt="like"><spanclass="feedback-form__btn-group_yes-btn">Yes</spanclass="feedback-form__btn-group_yes-btn"></label><input type="radio" name="useful" id="feedback__useful_no" value="false"><label for="feedback__useful_no"><img src="dislike.svg" class="small-img" alt="dislike"><spanclass="feedback-form__btn-group_no-btn">No</spanclass="feedback-form__btn-group_no-btn"></label></div><select name="category"><option disabled="">Please specify why</option><option value="bad_recommendation" selected="">Recommendations did not help me</option><option value="difficult_text">Article is hard to understand</option><option value="no_answer">Didn`t answer my question</option><option value="bad_header">Content does not match the topic</option><option value="other_reason">Other</option></select><input type="submit"></form></div><div class="found_typo"><p style="margin: 0px; margin-top: 16px !important;"><span><b>Found a typo?</b></span> Select it and press <i>Ctrl+Enter</i> to send us feedback</p></div></div>
|
||
|
||
</section>
|
||
</div>
|
||
<aside class="article__sidebar" style="display:none">
|
||
<input type="checkbox" />
|
||
<div class="article__arrow"></div>
|
||
<div class="table-of-contents elma365-right" id="toc2Content">
|
||
<h3 class="h3-toc">In this topic</h3>
|
||
<nav id="toc2"></nav>
|
||
</div>
|
||
</aside>
|
||
</div>
|
||
</article>
|
||
</main>
|
||
<footer class="footer">
|
||
<div class="footer-container">
|
||
<div class="footer-mobile">
|
||
|
||
<ul class="footer-mobile__list"><li><a href="https://brix365.com/en/" target="_blank">BRIX</a></li><li><a href="https://tssdk.brix365.com/en/latest/" target="_blank">SDK</a></li><li><a href="https://api.brix365.com/en/" target="_blank">API</a></li></ul><ul class="footer-mobile__list"><li><a href="https://brix365.com/en/help/platform/get-trial.html">Platform</a></li><li><a href="https://brix365.com/en/help/ecm/ecm-functions.html">ECM</a></li><li><a href="https://brix365.com/en/help/service/service-functions.html">Service</a></li><li><a href="https://brix365.com/en/help/projects/projects-functions.html">Projects</a></li></ul>
|
||
|
||
|
||
</div>
|
||
<div class="footer-wrap">
|
||
|
||
<div><span class="mobile-question-popup">Send feedback</span><form method="POST" action class="question__popup question-xs" id="question__popup"><div class="question-wrap"><span class="close"></span><span class="title">Ask a question</span><label for="help_question" style="display: none;"></label><textarea name="help_question" id="help_question"></textarea><input type="submit" value="Send"></div></form><div class="hidden fade-in question-success-xs">Sent</div></div>
|
||
|
||
<div class="footer-flex-b">
|
||
<span class="footer-copy">© 2025 BRIX</span>
|
||
<ul class="footer-list">
|
||
|
||
<li class="footer-item">
|
||
<a href="#" class="arrow-top" style="display: block;"></a>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
</footer>
|
||
<iframe name="hmnavigation" style="display:none!important"></iframe>
|
||
<script src="./jquery-ui.js"></script>
|
||
<!--script src="//cdn.jsdelivr.net/npm/featherlight@1.7.14/release/featherlight.min.js" type="text/javascript" charset="utf-8"></script-->
|
||
<script src="./jquery.tocify.min.js"></script>
|
||
<script src="./TypoReporter.min.js"></script>
|
||
<script src="./google-search.js"></script>
|
||
<script src="./main.js"></script>
|
||
<script type="text/javascript">
|
||
HMInitToggle('TOGGLE0186A1','hm.type','dropdown','hm.state','0');
|
||
HMInitToggle('TOGGLE0186A2','hm.type','dropdown','hm.state','0');
|
||
HMInitToggle('TOGGLE0186A3','hm.type','dropdown','hm.state','0');
|
||
HMInitToggle('TOGGLE0186A4','hm.type','dropdown','hm.state','0');
|
||
</script>
|
||
</body>
|
||
|
||
</html>
|