Remove obsolete kubernetes folder

This commit is contained in:
Robert Schäfer 2019-02-04 15:36:39 +01:00
parent 5492b282bc
commit cdf92cc6ea
7 changed files with 0 additions and 238 deletions

View File

@ -1,51 +0,0 @@
# Usage with minikube
Assuming you installed the packages git, docker ([all-distributions](https://docs.docker.com/install/)), minikube ([ubuntu]([minikube](https://computingforgeeks.com/how-to-install-minikube-on-ubuntu-18-04/)), [all-distributions](https://kubernetes.io/docs/tasks/tools/install-minikube/)) and virtualbox here...
First of all start minikube on your machine:
```sh
minikube start
```
You can always get an overview and see what's going on with your minikube:
```sh
minikube dashboard
```
From now on stay in your favorite work directory. First let's clone the necessary sources:
```sh
git clone https://github.com/Human-Connection/Nitro-Backend.git
git clone https://github.com/Human-Connection/Nitro-Web.git
```
Build Docker images, using the Minikube Docker daemon:
```sh
eval $(minikube docker-env)
docker build -t humanconnection/nitro-backend:latest Nitro-Backend/
docker build -t humanconnection/neo4j:latest -f Nitro-Backend/Dockerfile.neo4j Nitro-Backend/
```
Check that the image is in Minikubes Docker registry:
```sh
minikube ssh docker images
```
Now change into directory Nitro-Backend/kubernetes and create services and deployments:
```sh
cd Nitro-Backend/kubernetes
kubectl create -f neo4j-deployment.yaml,neo4j-data-persistentvolumeclaim.yaml,backend-deployment.yaml,neo4j-service.json,backend-service.json
```
You can see the backend in action with:
```sh
minikube service backend
```
### Troubleshoot
1. If you get an error message along th lines of 'The vboxdrv kernel module is not loaded.' - then you have the same issue i had. to solve this you need to install the propper linux kernel host modules package. Here an example for Manjaro:
https://forum.manjaro.org/t/installing-virtualbox-kernel-modules/6999
2. When you can not start minikube, try also to remove the cluster with `minikube delete` and start again with `minikube start`. Sometimes this fix startup problems of the cluster.
3. Now again you might run into trouble with an error like 'kubectl could not be found on your path.' In this case run the following command:
```sh
curl -Lo kubectl https://storage.googleapis.com/kubernetes-release/release/v1.10.0/bin/linux/amd64/kubectl && chmod +x kubectl && sudo cp kubectl /usr/local/bin/ && rm kubectl
```

View File

@ -1,41 +0,0 @@
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
annotations:
kompose.cmd: kompose convert -f ../docker-compose.yml
kompose.version: 1.16.0 (0c01309)
creationTimestamp: null
labels:
io.kompose.service: backend
name: backend
spec:
replicas: 1
strategy: {}
template:
metadata:
creationTimestamp: null
labels:
io.kompose.service: backend
spec:
containers:
- env:
- name: CLIENT_URI
value: http://localhost:3000
- name: GRAPHQL_PORT
value: "4000"
- name: GRAPHQL_URI
value: http://localhost:4000
- name: JWT_SECRET
value: b/&&7b78BF&fv/Vd
- name: MOCK
value: "false"
- name: NEO4J_URI
value: bolt://neo4j:7687
image: humanconnection/nitro-backend:latest
name: backend
ports:
- containerPort: 4000
resources: {}
imagePullPolicy: IfNotPresent
restartPolicy: Always
status: {}

View File

@ -1,35 +0,0 @@
{
"kind": "Service",
"apiVersion": "v1",
"metadata": {
"name": "backend",
"namespace": "default",
"selfLink": "/api/v1/namespaces/default/services/backend",
"uid": "57749bc1-dea3-11e8-ace2-080027b5d96d",
"resourceVersion": "8321",
"creationTimestamp": "2018-11-02T13:29:36Z",
"labels": {
"io.kompose.service": "backend"
}
},
"spec": {
"ports": [
{
"protocol": "TCP",
"port": 4000,
"targetPort": 4000,
"nodePort": 32633
}
],
"selector": {
"io.kompose.service": "backend"
},
"clusterIP": "10.110.129.92",
"type": "LoadBalancer",
"sessionAffinity": "None",
"externalTrafficPolicy": "Cluster"
},
"status": {
"loadBalancer": {}
}
}

View File

@ -1,14 +0,0 @@
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
name: kubernetes-dashboard
labels:
k8s-app: kubernetes-dashboard
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: kubernetes-dashboard
namespace: kube-system

View File

@ -1,14 +0,0 @@
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
creationTimestamp: null
labels:
io.kompose.service: neo4j-data
name: neo4j-data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 100Mi
status: {}

View File

@ -1,40 +0,0 @@
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
annotations:
kompose.cmd: kompose convert -f ../docker-compose.yml
kompose.version: 1.16.0 (0c01309)
creationTimestamp: null
labels:
io.kompose.service: neo4j
name: neo4j
spec:
replicas: 1
strategy:
type: Recreate
template:
metadata:
creationTimestamp: null
labels:
io.kompose.service: neo4j
spec:
containers:
- env:
- name: NEO4J_AUTH
value: none
image: humanconnection/neo4j:latest
name: neo4j
ports:
- containerPort: 7687
- containerPort: 7474
resources: {}
imagePullPolicy: IfNotPresent
volumeMounts:
- mountPath: /data
name: neo4j-data
restartPolicy: Always
volumes:
- name: neo4j-data
persistentVolumeClaim:
claimName: neo4j-data
status: {}

View File

@ -1,43 +0,0 @@
{
"kind": "Service",
"apiVersion": "v1",
"metadata": {
"name": "neo4j",
"namespace": "default",
"selfLink": "/api/v1/namespaces/default/services/neo4j",
"uid": "57de6181-dea3-11e8-ace2-080027b5d96d",
"resourceVersion": "8326",
"creationTimestamp": "2018-11-02T13:29:37Z",
"labels": {
"io.kompose.service": "neo4j"
}
},
"spec": {
"ports": [
{
"name": "port-1",
"protocol": "TCP",
"port": 7687,
"targetPort": 7687,
"nodePort": 30116
},
{
"name": "port-2",
"protocol": "TCP",
"port": 7474,
"targetPort": 7474,
"nodePort": 32658
}
],
"selector": {
"io.kompose.service": "neo4j"
},
"clusterIP": "10.108.175.122",
"type": "LoadBalancer",
"sessionAffinity": "None",
"externalTrafficPolicy": "Cluster"
},
"status": {
"loadBalancer": {}
}
}