**INFO** This isn't the best way to deploy to K8s, this is more of an example how simple it can be.
**INFO** This isn't the best way to deploy to K8s, this is more of an example how simple it can be.
The presentation can be found here: [Kubernetes - WYNTK - GitLab CI + Kubernetes Presentation](https://edenmal.moe/2017/07/31/Kubernetes-WYNTK-GitLab-CI-Kubernetes-Presentation/).
The presentation can be found here: [Kubernetes - WYNTK - GitLab CI + Kubernetes Presentation](https://edenmal.moe/post/2017/Kubernetes-WYNTK-GitLab-CI-Kubernetes-Presentation/).
The blog post these files were specifically used in is here: [GitLab + Kubernetes: Perfect Match for Continuous Delivery with Container](https://edenmal.moe/2017/07/04/GitLab-Kubernetes-Perfect-Match-for-Continuous-Delivery-with-Container/).
The blog post these files were specifically used in is here: [GitLab + Kubernetes: Perfect Match for Continuous Delivery with Container](https://edenmal.moe/post/2017/GitLab-Kubernetes-Perfect-Match-for-Continuous-Delivery-with-Container/).
...
@@ -11,3 +11,3 @@
...
@@ -11,3 +11,3 @@
An uptodate list of all my blog posts around GitLab and Kubernetes can be found on [this page](https://edenmal.moe/tags/GitLab/).
An uptodate list of all my blog posts around GitLab and Kubernetes can be found on [this page](https://edenmal.moe/tags/gitlab/).
This list is just an excerpt:
This list is just an excerpt:
...
@@ -13,9 +13,9 @@
...
@@ -13,9 +13,9 @@
This list is just an excerpt:
This list is just an excerpt:
*[GitLab + Kubernetes: Perfect Match for Continuous Delivery with Container](https://edenmal.moe/2017/07/04/GitLab-Kubernetes-Perfect-Match-for-Continuous-Delivery-with-Container/)
*[GitLab + Kubernetes: Perfect Match for Continuous Delivery with Container](https://edenmal.moe/post/2017/GitLab-Kubernetes-Perfect-Match-for-Continuous-Delivery-with-Container/)
*[Kubernetes - WYNTK - GitLab CI + Kubernetes Presentation](https://edenmal.moe/2017/07/31/Kubernetes-WYNTK-GitLab-CI-Kubernetes-Presentation/)
*[Kubernetes - WYNTK - GitLab CI + Kubernetes Presentation](https://edenmal.moe/post/2017/Kubernetes-WYNTK-GitLab-CI-Kubernetes-Presentation/)
*[GitLab + Kubernetes: Running CI Runners in Kubernetes](https://edenmal.moe/2017/08/31/GitLab-Kubernetes-Running-CI-Runners-in-Kubernetes/)
*[GitLab + Kubernetes: Running CI Runners in Kubernetes](https://edenmal.moe/post/2017/GitLab-Kubernetes-Running-CI-Runners-in-Kubernetes/)
*[GitLab + Kubernetes: GitLab on top of Kubernetes](https://edenmal.moe/2017/11/04/GitLab-Kubernetes-GitLab-on-top-of-Kubernetes/)
*[GitLab + Kubernetes: GitLab on top of Kubernetes](https://edenmal.moe/post/2017/GitLab-Kubernetes-GitLab-on-top-of-Kubernetes/)
*[GitLab: Use Keycloak as SAML 2.0 OmniAuth Provider](https://edenmal.moe/2018/01/16/GitLab-Keycloak-SAML-2-0-OmniAuth-Provider/)
*[GitLab: Use Keycloak as SAML 2.0 OmniAuth Provider](https://edenmal.moe/post/2018/GitLab-Keycloak-SAML-2-0-OmniAuth-Provider/)
## Requirements
## Requirements
The following points are required for this repository to work correctly:
The following points are required for this repository to work correctly:
...
@@ -30,8 +30,10 @@
...
@@ -30,8 +30,10 @@
## Using this repository
## Using this repository
You have to replace the following addresses in all files:
You have to replace the following addresses in all files:
*`gitlab.edenmal.net` with your GitLab address (example `gitlab.example.com`).
*`gitlab.zerbytes.net` with your GitLab address (e.g. `gitlab.example.com`).
*`registry.edenmal.net`/`registry.zerbytes.net` with your Docker Registry address (example `registry.example.com`).
*`registry.zerbytes.net` with your Docker registry address (e.g. `registry.example.com`).
*`edenmal.net` (in the Ingress manifest) with your Domain name.
*`edenmal.net` (in the Ingress manifest) with your domain name.
* You probably also want to change the subdomain name while you are at it.
*`presentatio-gitlab-k8s` with the Namespace name of your choice.
You also need to create a "Docker Login" Secret which contains your GitLab Registry access data (e.g. Username and Access token with registry access) named `regsecret` in the Namespace `presentation-gitlab-k8s`.
You also need to create a "Docker Login" Secret which contains your GitLab Registry access data (e.g. Username and Access token with registry access) named `regsecret` in the Namespace `presentation-gitlab-k8s`.
...
@@ -36,3 +38,4 @@
...
@@ -36,3 +38,4 @@
You also need to create a "Docker Login" Secret which contains your GitLab Registry access data (e.g. Username and Access token with registry access) named `regsecret` in the Namespace `presentation-gitlab-k8s`.
You also need to create a "Docker Login" Secret which contains your GitLab Registry access data (e.g. Username and Access token with registry access) named `regsecret` in the Namespace `presentation-gitlab-k8s`.
A guide for that can be found here: [Kubernetes.io - Pull an Image from a Private Registry](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/).
The Namespace manifest is in the [`gitlab-ci/`](/gitlab-ci/) directory.
The Namespace manifest is in the [`gitlab-ci/`](/gitlab-ci/) directory.
...
@@ -38,5 +41,4 @@
...
@@ -38,5 +41,4 @@
The Namespace manifest is in the [`gitlab-ci/`](/gitlab-ci/) directory.
The Namespace manifest is in the [`gitlab-ci/`](/gitlab-ci/) directory.
The guide for that can be found here: [Kubernetes.io - Pull an Image from a Private Registry](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/).
Then you can just import the repository into your GitLab instance and are ready to go.
Then you can just import the repository into your GitLab instance and are ready to go.