{"id":713,"date":"2018-10-27T06:07:30","date_gmt":"2018-10-27T06:07:30","guid":{"rendered":"https:\/\/www.appservgrid.com\/paw93\/?p=713"},"modified":"2018-10-28T05:41:15","modified_gmt":"2018-10-28T05:41:15","slug":"adopting-a-gke-cluster-with-rancher-2-0","status":"publish","type":"post","link":"https:\/\/www.appservgrid.com\/paw93\/index.php\/2018\/10\/27\/adopting-a-gke-cluster-with-rancher-2-0\/","title":{"rendered":"Adopting a GKE Cluster with Rancher 2.0"},"content":{"rendered":"

Rancher 2.0 is out<\/a> and
\nodds are, you\u2019re wondering what\u2019s so shiny and new about it. Well,
\nhere\u2019s a huge selling point for the next big Rancher release;
\nKubernetes cluster adoption! That\u2019s right, we here at Rancher wanted
\nmore kids, so we decided it was time to adopt. In all seriousness
\nthough, this feature helps make Rancher more relevant to developers who
\nalready have Kubernetes clusters deployed and are looking for a new way
\nto manage them. One of the most powerful aspects of this feature is that
\nit allows you to build a cluster from multiple cloud container engines,
\nincluding GKE, and keep them all under one management roof. In order to
\nadopt a GKE cluster into Rancher 2.0, you\u2019ll first need an instance of
\nRancher 2.0 running. To bootstrap a 2.0 server, check out this
\nguide here<\/a>. Stop
\nbefore selecting to Add Hosts and pop right back here when you\u2019re
\ndone.<\/p>\n

Acquiring your Kubectl Command<\/h2>\n

Now that you have a Rancher 2.0 server up and running, you\u2019ll be
\npresented with a page like the one below:<\/p>\n

\"RancherRancher 2.0 Home Page<\/em><\/p>\n

Of course, we want to select Use Existing Kubernetes as we\u2019re trying
\nto adopt an existing GKE cluster. On the next page, we\u2019re presented
\nwith a Host Registration URL menu, where we want to provide the
\npublicly accessible hostname and port for our Rancher server. As I set
\nup my host using a domain name in the form rancher.<domain>.<tld>,
\nRancher has already found the address for the site and defaults to the
\nproper hostname. If you\u2019re using a different network setup, just know
\nthat this hostname has to be accessible by all the machines in the
\nKubernetes cluster we are adopting. Click Save when you\u2019re finished
\nmaking your choice.<\/p>\n

\"HostHost Registration URL<\/em><\/p>\n

Now we are presented with a kubectl command which can be copied to
\nyour clipboard by clicking the little clipboard icon to the right of the
\ncommand. Copy the command and save it in a notepad to use later.<\/p>\n

\"KubectlKubectl Apply<\/em><\/p>\n

Important note: if you already have a cluster in GKE, you can skip
\nthe following section and go straight to Adopting a GKE
\nCluster<\/a><\/em><\/p>\n

Creating a GKE Cluster<\/h2>\n

Next, hop on over to your GKE control panel and, if you don\u2019t yet have
\na GKE cluster up and running, click the Create Cluster button.<\/p>\n

\"CreateCreate Cluster<\/em><\/p>\n

The cluster settings can be configured however you wish. I\u2019ll be using
\nthe name eric-rancher-demo, the us-central1-a zone,
\nversion 1.7.5-gke.1 (default) and 1vCPU, 2GB RAM machines. Leave the
\nOS as the Container-Optimized OS(cos) and all other settings at the
\ndefault. My finished settings looks like this:<\/p>\n

\"Container
\n[]<\/p>\n

You might want to grab some coffee after clicking Create, as GKE takes
\na while (5-10 minutes) to stand up your Kubernetes cluster.<\/p>\n

Adopting a GKE Cluster<\/h2>\n

Now that we have both a Rancher 2.0 server stood up and a GKE cluster
\nrunning and ready, we want to configure gcloud utils and kubectl to
\nconnect to our GKE cluster. In order to install gcloud utils on Debian
\nand Ubuntu based machines, follow the steps
\noutlined here<\/a> on
\nGoogle\u2019s website. For all other distros, find your
\nguide here<\/a>. Once we get
\nthe message gcloud has now been configured!, we can move onto the next
\nstep. To install kubectl all we need to do is
\ntype gcloud components install kubectl. Now that we
\nhave kubectl installed, in order to connect to our cluster, we want to
\nclick on the Connect to the cluster link at the top of the page in
\nGKE.<\/p>\n

\"ConnectConnect to the cluster<\/em><\/p>\n

A window will pop up providing instructions
\nto Configure kubectl command line access by running the following command.<\/p>\n

Copy that command and paste it into your terminal window. In this case:<\/p>\n

$ gcloud container clusters get-credentials eric-rancher-demo –zone us-central1-a –project rancher-dev
\n> Fetching cluster endpoint and auth data.
\n> kubeconfig entry generated for eric-rancher-demo.<\/p>\n

Our kubectl is now hooked up to the cluster. We should be able to
\nsimply paste the command from the Rancher 2.0 setup we did earlier, and
\nRancher will adopt the cluster.<\/p>\n

$ kubectl apply -f http:\/\/rancher.<domain>.<tld>\/v3\/scripts\/2CFC9454A034E7C3E367:1483142400000:feQRTz4WmIemlAUSy4O37vuF0.yaml
\n> namespace “cattle-system” created
\n> serviceaccount “rancher” created
\n> clusterrolebinding “rancher” created
\n> secret “rancher-credentials-39124a03” created
\n> pod “cluster-register-39124a03” created
\n> daemonset “rancher-agent” created<\/p>\n

Note: You cannot adopt a Kubernetes cluster if it has been previously
\nadopted by a Rancher 2.0 server unless you delete the
\nnamespace cattle-system from the Kubernetes installation. You can do
\nthis by typing kubectl delete –namespace cattle-system and waiting 5
\nminutes for the namespace to clear out.<\/em><\/p>\n

Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Rancher 2.0 is out and odds are, you\u2019re wondering what\u2019s so shiny and new about it. Well, here\u2019s a huge selling point for the next big Rancher release; Kubernetes cluster adoption! That\u2019s right, we here at Rancher wanted more kids, so we decided it was time to adopt. In all seriousness though, this feature helps … <\/p>\n

Continue reading “Adopting a GKE Cluster with Rancher 2.0”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-713","post","type-post","status-publish","format-standard","hentry","category-kubernetes"],"_links":{"self":[{"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/posts\/713","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/comments?post=713"}],"version-history":[{"count":1,"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/posts\/713\/revisions"}],"predecessor-version":[{"id":730,"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/posts\/713\/revisions\/730"}],"wp:attachment":[{"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/media?parent=713"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/categories?post=713"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/tags?post=713"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}