Skip to content
This repository was archived by the owner on Dec 9, 2024. It is now read-only.

documentation for running event-gateway on k8s #498

Merged
merged 33 commits into from
Aug 16, 2018
Merged
Show file tree
Hide file tree
Changes from 28 commits
Commits
Show all changes
33 commits
Select commit Hold shift + click to select a range
2ad08d1
adding more changes to README
sebito91 Aug 6, 2018
2f0c593
interim commit for more README updates
sebito91 Aug 6, 2018
ebb4f53
more updates to README
sebito91 Aug 6, 2018
0eb794c
adding in fedora section
sebito91 Aug 6, 2018
dc2f511
moving README one level higher
sebito91 Aug 6, 2018
fa79548
adding in ports description
sebito91 Aug 6, 2018
f7a1d7d
breaking up lines a bit
sebito91 Aug 6, 2018
ee5abf9
fixing the event url
sebito91 Aug 6, 2018
08570dd
adding in dev flag for running
sebito91 Aug 6, 2018
aacd0c9
adding example function register
sebito91 Aug 6, 2018
4d696d3
updating data
sebito91 Aug 7, 2018
6f3842e
updating for typo
sebito91 Aug 7, 2018
4bb0f4e
cleaning up k8s content
sebito91 Aug 14, 2018
29c5b8f
updating based on feedback
sebito91 Aug 14, 2018
c2df1e0
interim commit for k8s
sebito91 Aug 15, 2018
f9e143d
cleaning up helm files
sebito91 Aug 15, 2018
8cec6b0
moving to template variables
sebito91 Aug 15, 2018
e26e418
initial commit minikube readme
sebito91 Aug 15, 2018
22d2ed2
updating README
sebito91 Aug 15, 2018
ee9f732
updating number
sebito91 Aug 15, 2018
54dc823
updating formatting
sebito91 Aug 15, 2018
347c8b2
more formatting
sebito91 Aug 15, 2018
c1e699d
updating based upon feedback
sebito91 Aug 15, 2018
2040648
updating with trigger
sebito91 Aug 15, 2018
03b1bbc
updating the TOC
sebito91 Aug 15, 2018
ed8c510
updating based upon further feedback
sebito91 Aug 16, 2018
c46f730
updating with more feedback
sebito91 Aug 16, 2018
16765e8
updating to query all event types
sebito91 Aug 16, 2018
25a3e38
updating the README for the contrib level folder
sebito91 Aug 16, 2018
554216f
updating to builleted items
sebito91 Aug 16, 2018
0ba45ab
removing extraneous reference
sebito91 Aug 16, 2018
2153ab0
updating README with feedback
sebito91 Aug 16, 2018
1b8a70f
cleaning up doublenote
sebito91 Aug 16, 2018
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ If you don't want to run the Event Gateway yourself, you can use the hosted vers
There is a [official Docker image](https://hub.docker.com/r/serverless/event-gateway/).

```bash
docker run -p 4000:4000 -p 4001:4001 serverless/event-gateway -dev
docker run -p 4000:4000 -p 4001:4001 serverless/event-gateway --dev
```

### Binary
Expand All @@ -89,9 +89,14 @@ On Windows download [binary](https://github.com/serverless/event-gateway/release
Then run the binary in development mode with:

```bash
$ event-gateway -dev
$ event-gateway --dev
```

### Kubernetes
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do not point to the long readme file here. Only to MINIKUBE guide. I think it's worth to link "helm chart" to the /contrib/helm dir.


The repo contains `helm` charts for a quick deploy to an existing cluster using native nginx Ingress. To deploy
a development cluster you can follow the [minikube](contrib/helm/MINIKUBE.md) instructions.

---

If you want more detailed information on running and developing with the Event Gateway,
Expand Down
66 changes: 66 additions & 0 deletions contrib/helm/MINIKUBE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
# Event Gateway on Kubernetes (minikube)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doc is about setting up minikube. I think we should rename the title.


To develop and deploy the `event-gateway` and all related elements locally, the easiest method includes using
the [minikube](https://github.com/kubernetes/minikube) toolset. To get started, set up your local cluster with the
following instructions...

## Contents
1. [Fedora/RHEL/CentOS](#fedora-rhel-centos)
1. [Debian/Ubuntu](#debian-ubuntu)
1. [MacOS](#macos)

### Fedora/RHEL/CentOS
+ Install the prerequisite packages:
```bash
sudo dnf install kubernetes libvirt-daemon-kvm qemu-kvm nodejs docker
```

+ Ensure your user is added to the `libvirt` group for VM access. You can verify with `getent group libvirt` once done.
```bash
sudo usermod -a -G libvirt $(whoami)
```

+ Next, add the `libvirt` group to your current user grouplist. Verify by running `id` once done.
```bash
newgrp libvirt
```

+ Add the [docker-machine](https://github.com/docker/machine) binary to your system
```bash
curl -L https://github.com/docker/machine/releases/download/v0.15.0/docker-machine-$(uname -s)-$(uname -m) >/tmp/docker-machine && \
chmod +x /tmp/docker-machine && \
sudo cp /tmp/docker-machine /usr/local/bin/docker-machine
```

+ Add the CentOS `docker-machine` kvm driver. It's ok if you're not using CentOS as the driver should **still work**™
```bash
sudo curl -L https://github.com/dhiltgen/docker-machine-kvm/releases/download/v0.10.0/docker-machine-driver-kvm-centos7 > /tmp/docker-machine-driver-kvm && \
sudo chmod +x /tmp/docker-machine-driver-kvm && \
sudo mv /tmp/docker-machine-driver-kvm /usr/local/bin/docker-machine-driver-kvm
```

+ Download the minikube instance for your system
```bash
curl -Lo minikube https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 && \
sudo chmod +x minikube && \
sudo mv minikube /usr/local/bin/
```

+ Finally, start up your minikube service! **NOTE:** the instructions recommend using `kvm2` but please use the version that matches your system install
```bash
minikube start --vm-driver kvm2
```

+ Once everything is running you should be able to view your running cluster status
```bash
minikube status
minikube service kubernetes-dashboard --namespace kube-system
```

### Debian/Ubuntu

PENDING

### MacOS

PENDING
Loading