Replace GCE to GKE

parent e7611959
Pipeline #24661373 passed with stages
in 23 minutes
......@@ -296,9 +296,9 @@ For a complete list of pre-defined variables, have a look at the [variables docu
#### The `k8s-deploy` job
This job is responsible for deploying our application to the [Google Container Engine](https://cloud.google.com/container-engine/). I purposely decided to make use of the [Google Cloud SDK](https://cloud.google.com/sdk/gcloud/) (`gcloud`) because it gives us the possibility to programmatically create and manage Google Container Engine clusters and other products of the Google Cloud ecosystem. In this tutorial, we will simplify things a bit by creating the Google Container Engine cluster beforehand through the GUI.
This job is responsible for deploying our application to the [Google Kubernetes Engine](https://cloud.google.com/container-engine/). I purposely decided to make use of the [Google Cloud SDK](https://cloud.google.com/sdk/gcloud/) (`gcloud`) because it gives us the possibility to programmatically create and manage Google Container Engine clusters and other products of the Google Cloud ecosystem. In this tutorial, we will simplify things a bit by creating the Google Container Engine cluster beforehand through the GUI.
First, we create a Google Cloud Project named `actuator-sample`. Take note of the `Project ID` since it sometimes differs from the project name we specify. Then we create a Google Container Engine cluster named `actuator-sample` as well. We can choose any machine type and any number of nodes. For the purpose of this tutorial one node and a small machine are sufficient. Let's take note of the `zone`.
First, we create a Google Cloud Project named `actuator-sample`. Take note of the `Project ID` since it sometimes differs from the project name we specify. Then we create a Google Kubernetes Engine cluster named `actuator-sample` as well. We can choose any machine type and any number of nodes. For the purpose of this tutorial one node and a small machine are sufficient. Let's take note of the `zone`.
![Create a container cluster](/images/blogimages/continuous-delivery-of-a-spring-boot-application-with-gitlab-ci-and-kubernetes/create-gce-cluster.png){: .shadow}
......
---
title: "GitLab 8.16 released with auto deploy on Google Container Engine and Prometheus monitoring as part of GitLab"
title: "GitLab 8.16 released with auto deploy on Google Kubernetes Engine and Prometheus monitoring as part of GitLab"
categories: releases
author: Job van der Voort
author_twitter: Jobvo
......@@ -29,7 +29,7 @@ This month's Most Valuable Person ([MVP](/mvp/)) is
[more storage statistics](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7754).
Thanks Markus!
## From Cancun to Production on Google Container Engine (GKE)
## From Cancun to Production on Google Kubernetes Engine (GKE)
Every nine months all GitLab team members and their significant others are invited to [our summit](https://gitlab.com/summits/Summit-2017/).
This gives us the opportunity to bond in person and to share our ideas
......@@ -45,7 +45,7 @@ This was an internal presentation meant for our team members. We share it becaus
If you don't have the time to watch the full video, have a look at
[44:48][sid-challenge], where Sid gives a challenge to the present team:
> If you are the first one to present the idea to production demo working on Google Container Engine (GKE) on stage during the Summit, I will dance the Sid Shuffle from *Ice Age 4* on stage out of pure happiness.
> If you are the first one to present the idea to production demo working on Google Kubernetes Engine (GKE) on stage during the Summit, I will dance the Sid Shuffle from *Ice Age 4* on stage out of pure happiness.
If you're not familiar with the Sid shuffle, hold your breath. But first, the
context of the challenge:
......@@ -55,12 +55,12 @@ in a few minutes from a container scheduler without GitLab to deploying an app t
GitLab instance with auto-scaling CI. This powerful flow was only available
for people using Kubernetes in combination with Openshift, and [people asked](https://gitlab.com/gitlab-org/gitlab-ce/issues/25292) how they could replicate it.
Google Container Engine is a part of Google Cloud and can be used by anyone –
Google Kubernetes Engine is a part of Google Cloud and can be used by anyone –
getting it to work there is a big win for everyone. Motivated by both the
potential for developers around the world and that of seeing Sid dancing,
GitLab's engineers worked hard to make it happen.
You can deploy GitLab 8.16 straight to Google Container Engine, it will have
You can deploy GitLab 8.16 straight to Google Kubernetes Engine, it will have
auto-scaling CI, auto deploy to your own Kubernetes cluster, Mattermost,
use your private Docker registry and set up certificates using Let's Encrypt:
......@@ -78,7 +78,7 @@ Below is a less polished video of this same demo being given during the summit a
You can do everything shown in the _second_ video
right now [by signing up at Google Cloud][g-cloud] and simply following our
[documentation on idea to production on Google Container Engine][i2p-gke].
[documentation on idea to production on Google Kubernetes Engine][i2p-gke].
For deploying to Kubernetes, [see our documentation on auto deploy](https://docs.gitlab.com/ee/ci/autodeploy/index.html).
......
---
title: "Video tutorial: Idea to Production on Google Container Engine (GKE)"
title: "Video tutorial: Idea to Production on Google Kubernetes Engine (GKE)"
categories: engineering
author: Sean Packham
author_twitter: SeanPackham
......@@ -10,7 +10,7 @@ cta_button_text: Watch the <strong>8.16 release webcast</strong> live!
cta_button_link: https://page.gitlab.com/20170126_autodeploy_autodeploywebterminal.html
---
With GitLab 8.16 you can deploy GitLab straight to Google Container Engine (GKE) and go from Idea to Production in about 20 minutes, with auto-scaling CI, auto deploy, Mattermost, and a private Docker registry all on your own Kubernetes cluster. Watch the complete video tutorial to find out how you can take your team's productivity to the next level.
With GitLab 8.16 you can deploy GitLab straight to Google Kubernetes Engine (GKE) and go from Idea to Production in about 20 minutes, with auto-scaling CI, auto deploy, Mattermost, and a private Docker registry all on your own Kubernetes cluster. Watch the complete video tutorial to find out how you can take your team's productivity to the next level.
<!--more-->
......
......@@ -12,7 +12,7 @@ In this webcast, our Head of Product [Mark Pundsack](https://gitlab.com/markpund
<!-- more -->
With GitLab 8.15 and 8.16 we brought you auto deploy with Kubernetes using Google Container Engine, introduced our popular Time Tracking tool to the Community Edition, made it easier to fix bugs right within our UI with the Web Terminal, released monitoring functionality with Prometheus and added Merge Request Approvals to our Enterprise Edition. You can watch the recording of our release webcast and check out the highlights below.
With GitLab 8.15 and 8.16 we brought you auto deploy with Kubernetes using Google Kubernetes Engine, introduced our popular Time Tracking tool to the Community Edition, made it easier to fix bugs right within our UI with the Web Terminal, released monitoring functionality with Prometheus and added Merge Request Approvals to our Enterprise Edition. You can watch the recording of our release webcast and check out the highlights below.
<figure class="video_container">
<iframe src="https://www.youtube.com/embed/iYPhXm8RlxI" frameborder="0" allowfullscreen="true"> </iframe>
......
......@@ -43,7 +43,7 @@ name badge, stickers, bag patches, and a drawstring bag; all Mexican themed.
After a full night's rest we kicked the week off with a welcome keynote
by our main man, [Sid], who immediately got the team spirit going by
challenging the team to make the Idea to Production demo work on
Google Container Engine.
Google Kubernetes Engine.
<!-- Keynote -->
......
......@@ -5,7 +5,7 @@ author_gitlab: dzaporozhets
author_twitter: dzaporozhets
categories: engineering
image_title: '/images/blogimages/auto-deploy-google-cloud.jpg'
description: "How to get started with our auto deploy feature using Google Container Engine."
description: "How to get started with our auto deploy feature using Google Kubernetes Engine."
tags: google, GKE
---
......@@ -24,9 +24,9 @@ As per the documentation, the feature will package your application into a Docke
Setup of the GitLab auto deploy feature is a matter of clicking on the "Set up auto deploy" button and applying the "Kubernetes" template to your `.gitlab-ci.yml` file. However, before this, you need to configure your GitLab project with valid credentials so it can access your cluster. Which brings us to the point that you need your Kubernetes cluster first.
## Why Google Container Engine?
## Why Google Kubernetes Engine?
The documentation states, "Google Container Engine is a managed environment for deploying containerized applications." It runs Kubernetes and you can create your cluster with a few clicks in the web interface.
The documentation states, "Google Kubernetes Engine is a managed environment for deploying containerized applications." It runs Kubernetes and you can create your cluster with a few clicks in the web interface.
There are [a few other](https://kubernetes.io/docs/setup/pick-right-solution/) Kubernetes hosting solutions available on the market and you might prefer a different one, but as a newcomer I decided to go with Google for a few reasons:
......
......@@ -49,7 +49,7 @@ the case. With GitLab 10.1, a moderation tool is in place and you are able to
to avoid unnecessary friction among your community.
Going strong with our [DevOps vision](/2017/10/11/from-dev-to-devops/), we've
made it really easy to [create clusters on Google Container Engine from within
made it really easy to [create clusters on Google Kubernetes Engine from within
GitLab](#easy-creation-of-kubernetes-clusters-on-google-container-engine-(beta)).
The [online view of HTML artifacts](#online-view-of-html-artifacts)
is also another great addition that will make it even easier to view your test
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment