{"id":15852,"date":"2021-03-07T18:22:40","date_gmt":"2021-03-07T17:22:40","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/"},"modified":"2021-03-07T18:22:40","modified_gmt":"2021-03-07T17:22:40","slug":"rancher-up-and-running-on-ec2-1-one-node","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/","title":{"rendered":"Rancher, up and running, on EC2 – 1 – One node"},"content":{"rendered":"

If you want to play with Rancher<\/a> you have several options<\/a>, as outlined in the documentation. There are quick starts for the major public cloud providers (using Terraform<\/a>), you can install it on a Linux host by using the Rancher container or you can do it on your own. We’ll be doing it step by step, as I believe that gives most information on how things actually work. We’ll start with one node and then extend the Kubernetes cluster to three nodes and you’ll notice that this is actually quite easy and convenient using Rancher.<\/p>\n

<\/p>\n

I’ve created three Debian 10<\/a> EC2 instances:
\n\"\"<\/a><\/p>\n

We’ll start with the first one, and once it is ready, bring it to the latest release:<\/p>\n

\nadmin@ip-10-0-1-168:~$ sudo apt update && sudo apt dist-upgrade -y && sudo systemctl reboot\n<\/pre>\n
Once it is back, lets give it a more meaningful hostname:<\/p>\n
\nadmin@ip-10-0-1-168:~$ sudo hostnamectl set-hostname rancher1\nadmin@ip-10-0-1-168:~$ sudo bash\nsudo: unable to resolve host rancher1: Name or service not known\nroot@rancher1:\/home\/admin$ echo \"10.0.1.168 rancher1 rancher1.it.dbi-services.com\" >> \/etc\/hosts\nroot@rancher1:\/home\/admin$ exit\nexit\n<\/pre>\n
As Rancher depends on Docker<\/a>, we need to install a supported version of Docker. Range provides a script for this, which does all the work:<\/p>\n
\nadmin@ip-10-0-1-168:~$ sudo curl https:\/\/releases.rancher.com\/install-docker\/19.03.sh | sh\n  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n100 17251  100 17251    0     0   561k      0 --:--:-- --:--:-- --:--:--  561k\n+ sudo -E sh -c apt-get update\nHit:1 http:\/\/security.debian.org\/debian-security buster\/updates InRelease\nHit:2 http:\/\/cdn-aws.deb.debian.org\/debian buster InRelease\nHit:3 http:\/\/cdn-aws.deb.debian.org\/debian buster-updates InRelease\nHit:4 http:\/\/cdn-aws.deb.debian.org\/debian buster-backports InRelease\nReading package lists... Done\n...\n+ sudo -E sh -c docker version\nClient: Docker Engine - Community\n Version:           19.03.15\n API version:       1.40\n Go version:        go1.13.15\n Git commit:        99e3ed8919\n Built:             Sat Jan 30 03:17:05 2021\n OS\/Arch:           linux\/amd64\n Experimental:      false\n\nServer: Docker Engine - Community\n Engine:\n  Version:          19.03.15\n  API version:      1.40 (minimum version 1.12)\n  Go version:       go1.13.15\n  Git commit:       99e3ed8919\n  Built:            Sat Jan 30 03:15:34 2021\n  OS\/Arch:          linux\/amd64\n  Experimental:     false\n containerd:\n  Version:          1.4.3\n  GitCommit:        269548fa27e0089a8b8278fc4fc781d7f65a939b\n runc:\n  Version:          1.0.0-rc92\n  GitCommit:        ff819c7e9184c13b7c2607fe6c30ae19403a7aff\n docker-init:\n  Version:          0.18.0\n  GitCommit:        fec3683\n\nIf you would like to use Docker as a non-root user, you should now consider\nadding your user to the \"docker\" group with something like:\n\n  sudo usermod -aG docker admin\n\nRemember that you will have to log out and back in for this to take effect!\n\nWARNING: Adding a user to the \"docker\" group will grant the ability to run\n         containers which can be used to obtain root privileges on the\n         docker host.\n         Refer to https:\/\/docs.docker.com\/engine\/security\/security\/#docker-daemon-attack-surface\n         for more information.\n<\/pre>\n
We’ll be using the Rancher Kubernetes Engine (RKE)<\/a> and to get that onto the system, Rancher provides a single binary<\/a>. Before proceeding with that, we need a user, configure sudo (for convenience), and create the ssh keys:<\/p>\n
\nadmin@ip-10-0-1-168:~$ sudo groupadd rancher\nadmin@ip-10-0-1-168:~$ sudo useradd -g rancher -G docker -m -s \/bin\/bash rancher\nadmin@ip-10-0-1-168:~$ sudo passwd rancher\nNew password: \nRetype new password: \npasswd: password updated successfully\nadmin@ip-10-0-1-168:~$ sudo bash\nroot@rancher1:\/home\/admin$ echo \"rancher ALL=(ALL) NOPASSWD: ALL\" >> \/etc\/sudoers\nroot@rancher1:\/home\/admin$ su - rancher\nrancher@rancher1:~$ ssh-keygen \nGenerating public\/private rsa key pair.\nEnter file in which to save the key (\/home\/rancher\/.ssh\/id_rsa): \nCreated directory '\/home\/rancher\/.ssh'.\nEnter passphrase (empty for no passphrase): \nEnter same passphrase again: \nYour identification has been saved in \/home\/rancher\/.ssh\/id_rsa.\nYour public key has been saved in \/home\/rancher\/.ssh\/id_rsa.pub.\nThe key fingerprint is:\nSHA256:gHzFXkMttTw8dks64+1zEpt3Oef6TWs\/pKoiYDDruIk rancher@rancher1\nThe key's randomart image is:\n+---[RSA 2048]----+\n|       ....o.    |\n|   . . .. +o..   |\n|    o o. . oB o  |\n| o   . ..  . * . |\n|  +     S   + .  |\n| . o       . +.. |\n|o . .       . ++o|\n|oo   . .     o=*B|\n|E.    . ..... +X@|\n+----[SHA256]-----+\nrancher@rancher1:~$ cat .ssh\/id_rsa.pub >> .ssh\/authorized_keys\nrancher@rancher1:~$ ssh rancher@rancher1\nLinux rancher1 4.19.0-14-cloud-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64\n\nThe programs included with the Debian GNU\/Linux system are free software;\nthe exact distribution terms for each program are described in the\nindividual files in \/usr\/share\/doc\/*\/copyright.\n\nDebian GNU\/Linux comes with ABSOLUTELY NO WARRANTY, to the extent\npermitted by applicable law.\n<\/pre>\n
That’s it for the requirements to get started. Download the RKE binary:<\/p>\n
\nrancher@rancher1:~$ wget https:\/\/github.com\/rancher\/rke\/releases\/download\/v1.1.15\/rke_linux-amd64\nrancher@rancher1:~$ mv rke_linux-amd64 rke\nrancher@rancher1:~$ sudo mv rke \/usr\/local\/bin\/\nrancher@rancher1:~$ sudo chown rancher:rancher \/usr\/local\/bin\/rke\nrancher@rancher1:~$ sudo chmod 750 \/usr\/local\/bin\/rke\nrancher@rancher1:~$ rke --version\nrke version v1.1.15\n<\/pre>\n
All you need to do, to get RKE setup on a single host is this:<\/p>\n
\nrancher@rancher1:~$ rke config\n[+] Cluster Level SSH Private Key Path [~\/.ssh\/id_rsa]: \n[+] Number of Hosts [1]: \n[+] SSH Address of host (1) [none]: 10.0.1.168\n[+] SSH Port of host (1) [22]: \n[+] SSH Private Key Path of host (10.0.1.168) [none]: \n[-] You have entered empty SSH key path, trying fetch from SSH key parameter\n[+] SSH Private Key of host (10.0.1.168) [none]: \n[-] You have entered empty SSH key, defaulting to cluster level SSH key: ~\/.ssh\/id_rsa\n[+] SSH User of host (10.0.1.168) [ubuntu]: rancher\n[+] Is host (10.0.1.168) a Control Plane host (y\/n)? [y]: \n[+] Is host (10.0.1.168) a Worker host (y\/n)? [n]: y\n[+] Is host (10.0.1.168) an etcd host (y\/n)? [n]: y\n[+] Override Hostname of host (10.0.1.168) [none]: \n[+] Internal IP of host (10.0.1.168) [none]: 10.0.1.168\n[+] Docker socket path on host (10.0.1.168) [\/var\/run\/docker.sock]: \n[+] Network Plugin Type (flannel, calico, weave, canal) [canal]: \n[+] Authentication Strategy [x509]: \n[+] Authorization Mode (rbac, none) [rbac]: \n[+] Kubernetes Docker image [rancher\/hyperkube:v1.18.16-rancher1]: \n[+] Cluster domain [cluster.local]: \n[+] Service Cluster IP Range [10.43.0.0\/16]: \n[+] Enable PodSecurityPolicy [n]: \n[+] Cluster Network CIDR [10.42.0.0\/16]: \n[+] Cluster DNS Service IP [10.43.0.10]: \n[+] Add addon manifest URLs or YAML files [no]: \n<\/pre>\n
This creates the cluster configuration file:<\/p>\n
\nrancher@rancher1:~$ ls -la cluster.yml \n-rw-r----- 1 rancher rancher 4619 Mar  6 14:40 cluster.yml\n<\/pre>\n
Bring it up:<\/p>\n
\nrancher@rancher1:~$ rke up\nINFO[0000] Running RKE version: v1.1.15                 \nINFO[0000] Initiating Kubernetes cluster                \nINFO[0000] [dialer] Setup tunnel for host [10.0.1.168]  \n...\nINFO[0157] [addons] Successfully saved ConfigMap for addon rke-ingress-controller to Kubernetes \nINFO[0157] [addons] Executing deploy job rke-ingress-controller \nINFO[0162] [ingress] ingress controller nginx deployed successfully \nINFO[0162] [addons] Setting up user addons              \nINFO[0162] [addons] no user addons defined              \nINFO[0162] Finished building Kubernetes cluster successfully \n<\/pre>\n
That’s it. The one node Kubernetes cluster is ready (Control Plane, worker and etcd all on one host). This is of course nothing you’d do in a serious deployment, but to get started this is fine. To talk to the Kubernetes cluster you shoud install kubectl<\/a>:<\/p>\n
\nrancher@rancher1:~$ curl -LO \"https:\/\/storage.googleapis.com\/kubernetes-release\/release\/$(curl -s https:\/\/storage.googleapis.com\/kubernetes-release\/release\/stable.txt)\/bin\/linux\/amd64\/kubectl\"\n  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n100 38.3M  100 38.3M    0     0  73.9M      0 --:--:-- --:--:-- --:--:-- 73.8M\n<\/pre>\n
Same procedure as with the rke binary:<\/p>\n
\nrancher@rancher1:~$ ls\ncluster.rkestate  cluster.yml  kube_config_cluster.yml  kubectl\nrancher@rancher1:~$ sudo mv kubectl \/usr\/local\/bin\/\nrancher@rancher1:~$ sudo chown rancher:rancher \/usr\/local\/bin\/kubectl\nrancher@rancher1:~$ sudo chmod 750 \/usr\/local\/bin\/kubectl\n<\/pre>\n
Use it to talk to your cluster:<\/p>\n
\nrancher@rancher1:~$ export KUBECONFIG=kube_config_cluster.yml \nrancher@rancher1:~$ kubectl get namespace\nNAME              STATUS   AGE\ndefault           Active   6m31s\ningress-nginx     Active   5m36s\nkube-node-lease   Active   6m33s\nkube-public       Active   6m33s\nkube-system       Active   6m33s\n<\/pre>\n
Done. RKE is up and running on a single node. Be aware that we did not yet install Ranger, just RKE. But also notice how easy that was: We have a Kubernetes cluster running, and all we needed to do, took around 10 minutes. In the next post we’ll extend the configuration to three nodes.<\/p>\n","protected":false},"excerpt":{"rendered":"
If you want to play with Rancher you have several options, as outlined in the documentation. There are quick starts for the major public cloud providers (using Terraform), you can install it on a Linux host by using the Rancher container or you can do it on your own. We’ll be doing it step by […]<\/p>\n","protected":false},"author":29,"featured_media":15853,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1865,1320,1522],"tags":[89,2276,309],"type_dbi":[],"class_list":["post-15852","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aws","category-devops","category-kubernetes","tag-kubernetes","tag-rancher","tag-suse"],"acf":[],"yoast_head":"\nRancher, up and running, on EC2 - 1 - One node - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Rancher, up and running, on EC2 - 1 - One node\" \/>\n<meta property=\"og:description\" content=\"If you want to play with Rancher you have several options, as outlined in the documentation. There are quick starts for the major public cloud providers (using Terraform), you can install it on a Linux host by using the Rancher container or you can do it on your own. We’ll be doing it step by […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2021-03-07T17:22:40+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rancher_1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1430\" \/>\n\t<meta property=\"og:image:height\" content=\"112\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Daniel Westermann\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@westermanndanie\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Daniel Westermann\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/rancher-up-and-running-on-ec2-1-one-node\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/rancher-up-and-running-on-ec2-1-one-node\\\/\"},\"author\":{\"name\":\"Daniel Westermann\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"headline\":\"Rancher, up and running, on EC2 – 1 – One node\",\"datePublished\":\"2021-03-07T17:22:40+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/rancher-up-and-running-on-ec2-1-one-node\\\/\"},\"wordCount\":361,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/rancher-up-and-running-on-ec2-1-one-node\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/rancher_1.jpg\",\"keywords\":[\"kubernetes\",\"Rancher\",\"SuSE\"],\"articleSection\":[\"AWS\",\"DevOps\",\"Kubernetes\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/rancher-up-and-running-on-ec2-1-one-node\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/rancher-up-and-running-on-ec2-1-one-node\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/rancher-up-and-running-on-ec2-1-one-node\\\/\",\"name\":\"Rancher, up and running, on EC2 - 1 - One node - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/rancher-up-and-running-on-ec2-1-one-node\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/rancher-up-and-running-on-ec2-1-one-node\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/rancher_1.jpg\",\"datePublished\":\"2021-03-07T17:22:40+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/rancher-up-and-running-on-ec2-1-one-node\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/rancher-up-and-running-on-ec2-1-one-node\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/rancher-up-and-running-on-ec2-1-one-node\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/rancher_1.jpg\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/rancher_1.jpg\",\"width\":1430,\"height\":112},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/rancher-up-and-running-on-ec2-1-one-node\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Rancher, up and running, on EC2 – 1 – One node\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d08e9bd996a89bd75c0286cbabf3c66\",\"name\":\"Daniel Westermann\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"caption\":\"Daniel Westermann\"},\"description\":\"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\\\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.\",\"sameAs\":[\"https:\\\/\\\/x.com\\\/westermanndanie\"],\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/daniel-westermann\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Rancher, up and running, on EC2 - 1 - One node - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/","og_locale":"en_US","og_type":"article","og_title":"Rancher, up and running, on EC2 - 1 - One node","og_description":"If you want to play with Rancher you have several options, as outlined in the documentation. There are quick starts for the major public cloud providers (using Terraform), you can install it on a Linux host by using the Rancher container or you can do it on your own. We’ll be doing it step by […]","og_url":"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/","og_site_name":"dbi Blog","article_published_time":"2021-03-07T17:22:40+00:00","og_image":[{"width":1430,"height":112,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rancher_1.jpg","type":"image\/jpeg"}],"author":"Daniel Westermann","twitter_card":"summary_large_image","twitter_creator":"@westermanndanie","twitter_misc":{"Written by":"Daniel Westermann","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/"},"author":{"name":"Daniel Westermann","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"headline":"Rancher, up and running, on EC2 – 1 – One node","datePublished":"2021-03-07T17:22:40+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/"},"wordCount":361,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rancher_1.jpg","keywords":["kubernetes","Rancher","SuSE"],"articleSection":["AWS","DevOps","Kubernetes"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/","url":"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/","name":"Rancher, up and running, on EC2 - 1 - One node - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rancher_1.jpg","datePublished":"2021-03-07T17:22:40+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rancher_1.jpg","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rancher_1.jpg","width":1430,"height":112},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/rancher-up-and-running-on-ec2-1-one-node\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Rancher, up and running, on EC2 – 1 – One node"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66","name":"Daniel Westermann","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","caption":"Daniel Westermann"},"description":"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.","sameAs":["https:\/\/x.com\/westermanndanie"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/15852","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=15852"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/15852\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/15853"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=15852"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=15852"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=15852"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=15852"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}