Initial commit

README.md

@@ -1,2 +0,0 @@
-# Rancher
-

Sebastians/Nexus3/Nexus3-claim0-persistentvolumeclaim.yaml

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

Sebastians/Nexus3/Nexus3-deployment.yaml

@@ -0,0 +1,40 @@
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+  creationTimestamp: null
+  labels:
+    io.kompose.service: Nexus3
+  name: Nexus3
+spec:
+  replicas: 0
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      creationTimestamp: null
+      labels:
+        io.kompose.service: Nexus3
+    spec:
+      containers:
+      - image: sonatype/nexus3
+        name: Nexus3
+        ports:
+        - containerPort: 8081
+        - containerPort: 8082
+        resources: {}
+        stdin: true
+        tty: true
+        volumeMounts:
+        - mountPath: /nexus-data
+          name: Nexus3-claim0
+      restartPolicy: Always
+      volumes:
+      - name: Nexus3-claim0
+        persistentVolumeClaim:
+          claimName: Nexus3-claim0
+status: {}

Sebastians/Nexus3/Nexus3-service.yaml

@@ -0,0 +1,24 @@
+apiVersion: v1
+kind: Service
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+  creationTimestamp: null
+  labels:
+    io.kompose.service: Nexus3
+  name: Nexus3
+spec:
+  ports:
+  - name: "8081"
+    port: 8081
+    targetPort: 8081
+  - name: "8082"
+    port: 8082
+    targetPort: 8082
+  selector:
+    io.kompose.service: Nexus3
+status:
+  loadBalancer: {}

Sebastians/Nexus3/README.md

@@ -0,0 +1,13 @@
+Some Rancher v1.x organizational concepts have changed in racher v2.x:
+
+- environments -> projects
+- stacks -> namespaces 
+- services -> workloads
+
+To maintain same organization boundaries on rancher v2.x, is recommended to:
+
+- create a separated project for every rancher v1.x environment.
+- create a separated namespace for every rancher v1.x stack.
+
+Project: Sebastians
+Namespace: Nexus3

Sebastians/Nexus3/docker-compose.yml

@@ -0,0 +1,13 @@
+version: '2'
+services:
+  Nexus3:
+    image: sonatype/nexus3
+    stdin_open: true
+    volumes:
+    - /mnt/volume-data/nexus-data/nexus-data:/nexus-data
+    tty: true
+    ports:
+    - 8081:8081/tcp
+    - 8082:8082/tcp
+    labels:
+      io.rancher.container.pull_image: always

Sebastians/Nexus3/output.txt

@@ -0,0 +1,17 @@
+## This is the service-wise list of constructs that need to be handled specially.
+Please refer https://rancher.com/docs/rancher/v2.x/en/v1.6-migration/ to transition these to Rancher 2.0.
+Nexus3:
+  labels:
+    >>io.rancher.container.pull_image
+  ports:
+    Refer: https://rancher.com/blog/2018/2018-08-14-expose-and-monitor-workloads/
+    Please add a hostPort or a nodePort to your Kubernetes workload to expose the ports used.
+  scale:
+  start_on_create:
+  volumes:
+
+## More Docker/Rancher1.6 constructs that need to be transitioned to Kubernetes/Rancher 2.0 in a special way:
+  Rancher Metadata - Incase your applications depend on metadata.
+  Rancher 1.6 FQDN resolution format
+
+Please contact Rancher Support for more help to migrate these to Rancher 2.0, as there is no direct translation available.

Sebastians/Nexus3/rancher-compose.yml

@@ -0,0 +1,5 @@
+version: '2'
+services:
+  Nexus3:
+    scale: 1
+    start_on_create: true

Sebastians/gogs/README.md

@@ -0,0 +1,13 @@
+Some Rancher v1.x organizational concepts have changed in racher v2.x:
+
+- environments -> projects
+- stacks -> namespaces 
+- services -> workloads
+
+To maintain same organization boundaries on rancher v2.x, is recommended to:
+
+- create a separated project for every rancher v1.x environment.
+- create a separated namespace for every rancher v1.x stack.
+
+Project: Sebastians
+Namespace: gogs

Sebastians/gogs/docker-compose.yml

@@ -0,0 +1,28 @@
+version: '2'
+services:
+  gogs:
+    image: gogs/gogs:latest
+    environment:
+      DISABLE_REGISTRATION: 'true'
+      RUN_CROND: 'true'
+      SHOW_REGISTRATION_BUTTON: 'false'
+    volumes:
+    - /mnt/volume-data/gogs/gogs-data:/data
+    links:
+    - postgres:database
+    - postgres:postgres
+    ports:
+    - 2222:22/tcp
+    - 3000:3000/tcp
+    labels:
+      io.rancher.container.pull_image: always
+  postgres:
+    image: postgres:9.5
+    environment:
+      POSTGRES_DB: gogs
+      POSTGRES_PASSWORD: vergessen1974
+      POSTGRES_USER: Sebastian
+    volumes:
+    - /mnt/volume-data/gogs/db-data:/var/lib/postgresql/data
+    labels:
+      io.rancher.container.pull_image: always

Sebastians/gogs/gogs-claim0-persistentvolumeclaim.yaml

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

Sebastians/gogs/gogs-deployment.yaml

@@ -0,0 +1,45 @@
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+  creationTimestamp: null
+  labels:
+    io.kompose.service: gogs
+  name: gogs
+spec:
+  replicas: 0
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      creationTimestamp: null
+      labels:
+        io.kompose.service: gogs
+    spec:
+      containers:
+      - env:
+        - name: DISABLE_REGISTRATION
+          value: "true"
+        - name: RUN_CROND
+          value: "true"
+        - name: SHOW_REGISTRATION_BUTTON
+          value: "false"
+        image: gogs/gogs:latest
+        name: gogs
+        ports:
+        - containerPort: 22
+        - containerPort: 3000
+        resources: {}
+        volumeMounts:
+        - mountPath: /data
+          name: gogs-claim0
+      restartPolicy: Always
+      volumes:
+      - name: gogs-claim0
+        persistentVolumeClaim:
+          claimName: gogs-claim0
+status: {}

Sebastians/gogs/gogs-service.yaml

@@ -0,0 +1,24 @@
+apiVersion: v1
+kind: Service
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+  creationTimestamp: null
+  labels:
+    io.kompose.service: gogs
+  name: gogs
+spec:
+  ports:
+  - name: "2222"
+    port: 2222
+    targetPort: 22
+  - name: "3000"
+    port: 3000
+    targetPort: 3000
+  selector:
+    io.kompose.service: gogs
+status:
+  loadBalancer: {}

Sebastians/gogs/output.txt

@@ -0,0 +1,26 @@
+## This is the service-wise list of constructs that need to be handled specially.
+Please refer https://rancher.com/docs/rancher/v2.x/en/v1.6-migration/ to transition these to Rancher 2.0.
+gogs:
+  labels:
+    >>io.rancher.container.pull_image
+  links:
+    Refer: https://rancher.com/blog/2018/2018-09-04-service_discovery_2dot0/
+    Please add the necessary Service Discovery Records for your Rancher 2.0 Kubernetes workload to implement the links.
+  ports:
+    Refer: https://rancher.com/blog/2018/2018-08-14-expose-and-monitor-workloads/
+    Please add a hostPort or a nodePort to your Kubernetes workload to expose the ports used.
+  scale:
+  start_on_create:
+  volumes:
+postgres:
+  labels:
+    >>io.rancher.container.pull_image
+  scale:
+  start_on_create:
+  volumes:
+
+## More Docker/Rancher1.6 constructs that need to be transitioned to Kubernetes/Rancher 2.0 in a special way:
+  Rancher Metadata - Incase your applications depend on metadata.
+  Rancher 1.6 FQDN resolution format
+
+Please contact Rancher Support for more help to migrate these to Rancher 2.0, as there is no direct translation available.

Sebastians/gogs/postgres-claim0-persistentvolumeclaim.yaml

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

Sebastians/gogs/postgres-deployment.yaml

@@ -0,0 +1,42 @@
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+  creationTimestamp: null
+  labels:
+    io.kompose.service: postgres
+  name: postgres
+spec:
+  replicas: 0
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      creationTimestamp: null
+      labels:
+        io.kompose.service: postgres
+    spec:
+      containers:
+      - env:
+        - name: POSTGRES_DB
+          value: gogs
+        - name: POSTGRES_PASSWORD
+          value: vergessen1974
+        - name: POSTGRES_USER
+          value: Sebastian
+        image: postgres:9.5
+        name: postgres
+        resources: {}
+        volumeMounts:
+        - mountPath: /var/lib/postgresql/data
+          name: postgres-claim0
+      restartPolicy: Always
+      volumes:
+      - name: postgres-claim0
+        persistentVolumeClaim:
+          claimName: postgres-claim0
+status: {}

Sebastians/gogs/rancher-compose.yml

@@ -0,0 +1,8 @@
+version: '2'
+services:
+  gogs:
+    scale: 1
+    start_on_create: true
+  postgres:
+    scale: 1
+    start_on_create: true

Sebastians/koken/README.md

@@ -0,0 +1,13 @@
+Some Rancher v1.x organizational concepts have changed in racher v2.x:
+
+- environments -> projects
+- stacks -> namespaces 
+- services -> workloads
+
+To maintain same organization boundaries on rancher v2.x, is recommended to:
+
+- create a separated project for every rancher v1.x environment.
+- create a separated namespace for every rancher v1.x stack.
+
+Project: Sebastians
+Namespace: koken

Sebastians/koken/docker-compose.yml

@@ -0,0 +1,13 @@
+version: '2'
+services:
+  koken:
+    image: malteo/docker-koken-lemp
+    stdin_open: true
+    volumes:
+    - /mnt/koken/www:/usr/share/nginx/www
+    - /mnt/koken/mysql:/var/lib/mysql
+    tty: true
+    ports:
+    - 83:8080/tcp
+    labels:
+      io.rancher.container.pull_image: always

Sebastians/koken/koken-claim0-persistentvolumeclaim.yaml

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

Sebastians/koken/koken-claim1-persistentvolumeclaim.yaml

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

Sebastians/koken/koken-deployment.yaml

@@ -0,0 +1,44 @@
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+  creationTimestamp: null
+  labels:
+    io.kompose.service: koken
+  name: koken
+spec:
+  replicas: 0
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      creationTimestamp: null
+      labels:
+        io.kompose.service: koken
+    spec:
+      containers:
+      - image: malteo/docker-koken-lemp
+        name: koken
+        ports:
+        - containerPort: 8080
+        resources: {}
+        stdin: true
+        tty: true
+        volumeMounts:
+        - mountPath: /usr/share/nginx/www
+          name: koken-claim0
+        - mountPath: /var/lib/mysql
+          name: koken-claim1
+      restartPolicy: Always
+      volumes:
+      - name: koken-claim0
+        persistentVolumeClaim:
+          claimName: koken-claim0
+      - name: koken-claim1
+        persistentVolumeClaim:
+          claimName: koken-claim1
+status: {}

Sebastians/koken/koken-service.yaml

@@ -0,0 +1,21 @@
+apiVersion: v1
+kind: Service
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+  creationTimestamp: null
+  labels:
+    io.kompose.service: koken
+  name: koken
+spec:
+  ports:
+  - name: "83"
+    port: 83
+    targetPort: 8080
+  selector:
+    io.kompose.service: koken
+status:
+  loadBalancer: {}

Sebastians/koken/output.txt

@@ -0,0 +1,17 @@
+## This is the service-wise list of constructs that need to be handled specially.
+Please refer https://rancher.com/docs/rancher/v2.x/en/v1.6-migration/ to transition these to Rancher 2.0.
+koken:
+  labels:
+    >>io.rancher.container.pull_image
+  ports:
+    Refer: https://rancher.com/blog/2018/2018-08-14-expose-and-monitor-workloads/
+    Please add a hostPort or a nodePort to your Kubernetes workload to expose the ports used.
+  scale:
+  start_on_create:
+  volumes:
+
+## More Docker/Rancher1.6 constructs that need to be transitioned to Kubernetes/Rancher 2.0 in a special way:
+  Rancher Metadata - Incase your applications depend on metadata.
+  Rancher 1.6 FQDN resolution format
+
+Please contact Rancher Support for more help to migrate these to Rancher 2.0, as there is no direct translation available.

Sebastians/koken/rancher-compose.yml

@@ -0,0 +1,5 @@
+version: '2'
+services:
+  koken:
+    scale: 1
+    start_on_create: true

Sebastians/matomo/README.md

@@ -0,0 +1,13 @@
+Some Rancher v1.x organizational concepts have changed in racher v2.x:
+
+- environments -> projects
+- stacks -> namespaces 
+- services -> workloads
+
+To maintain same organization boundaries on rancher v2.x, is recommended to:
+
+- create a separated project for every rancher v1.x environment.
+- create a separated namespace for every rancher v1.x stack.
+
+Project: Sebastians
+Namespace: matomo

Sebastians/matomo/docker-compose.yml

@@ -0,0 +1,32 @@
+version: '2'
+services:
+  matomo:
+    image: matomo
+    environment:
+      GID: '1000'
+      UID: '1000'
+    stdin_open: true
+    volumes:
+    - /mnt/matomo/config:/var/www/html/config
+    tty: true
+    links:
+    - matomo-db:db_matomo
+    ports:
+    - 82:80/tcp
+    labels:
+      io.rancher.container.pull_image: always
+  matomo-db:
+    image: mariadb:latest
+    environment:
+      MYSQL_ROOT_PASSWORD: vergessen1974
+      MYSQL_DATABASE: matomo
+      MYSQL_USER: matomo
+      MYSQL_PASSWORD: vergessen1974
+    stdin_open: true
+    volumes:
+    - /mnt/matomo/db:/var/lib/mysql
+    tty: true
+    command:
+    - --max_allowed_packet=72505856
+    labels:
+      io.rancher.container.pull_image: always

Sebastians/matomo/matomo-claim0-persistentvolumeclaim.yaml

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

Sebastians/matomo/matomo-db-claim0-persistentvolumeclaim.yaml

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

Sebastians/matomo/matomo-db-deployment.yaml

@@ -0,0 +1,48 @@
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+  creationTimestamp: null
+  labels:
+    io.kompose.service: matomo-db
+  name: matomo-db
+spec:
+  replicas: 0
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      creationTimestamp: null
+      labels:
+        io.kompose.service: matomo-db
+    spec:
+      containers:
+      - args:
+        - --max_allowed_packet=72505856
+        env:
+        - name: MYSQL_DATABASE
+          value: matomo
+        - name: MYSQL_PASSWORD
+          value: vergessen1974
+        - name: MYSQL_ROOT_PASSWORD
+          value: vergessen1974
+        - name: MYSQL_USER
+          value: matomo
+        image: mariadb:latest
+        name: matomo-db
+        resources: {}
+        stdin: true
+        tty: true
+        volumeMounts:
+        - mountPath: /var/lib/mysql
+          name: matomo-db-claim0
+      restartPolicy: Always
+      volumes:
+      - name: matomo-db-claim0
+        persistentVolumeClaim:
+          claimName: matomo-db-claim0
+status: {}

Sebastians/matomo/matomo-deployment.yaml

@@ -0,0 +1,44 @@
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+  creationTimestamp: null
+  labels:
+    io.kompose.service: matomo
+  name: matomo
+spec:
+  replicas: 0
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      creationTimestamp: null
+      labels:
+        io.kompose.service: matomo
+    spec:
+      containers:
+      - env:
+        - name: GID
+          value: "1000"
+        - name: UID
+          value: "1000"
+        image: matomo
+        name: matomo
+        ports:
+        - containerPort: 80
+        resources: {}
+        stdin: true
+        tty: true
+        volumeMounts:
+        - mountPath: /var/www/html/config
+          name: matomo-claim0
+      restartPolicy: Always
+      volumes:
+      - name: matomo-claim0
+        persistentVolumeClaim:
+          claimName: matomo-claim0
+status: {}

Sebastians/matomo/matomo-service.yaml

@@ -0,0 +1,21 @@
+apiVersion: v1
+kind: Service
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+  creationTimestamp: null
+  labels:
+    io.kompose.service: matomo
+  name: matomo
+spec:
+  ports:
+  - name: "82"
+    port: 82
+    targetPort: 80
+  selector:
+    io.kompose.service: matomo
+status:
+  loadBalancer: {}

Sebastians/matomo/output.txt

@@ -0,0 +1,26 @@
+## This is the service-wise list of constructs that need to be handled specially.
+Please refer https://rancher.com/docs/rancher/v2.x/en/v1.6-migration/ to transition these to Rancher 2.0.
+matomo:
+  labels:
+    >>io.rancher.container.pull_image
+  links:
+    Refer: https://rancher.com/blog/2018/2018-09-04-service_discovery_2dot0/
+    Please add the necessary Service Discovery Records for your Rancher 2.0 Kubernetes workload to implement the links.
+  ports:
+    Refer: https://rancher.com/blog/2018/2018-08-14-expose-and-monitor-workloads/
+    Please add a hostPort or a nodePort to your Kubernetes workload to expose the ports used.
+  scale:
+  start_on_create:
+  volumes:
+matomo-db:
+  labels:
+    >>io.rancher.container.pull_image
+  scale:
+  start_on_create:
+  volumes:
+
+## More Docker/Rancher1.6 constructs that need to be transitioned to Kubernetes/Rancher 2.0 in a special way:
+  Rancher Metadata - Incase your applications depend on metadata.
+  Rancher 1.6 FQDN resolution format
+
+Please contact Rancher Support for more help to migrate these to Rancher 2.0, as there is no direct translation available.

Sebastians/matomo/rancher-compose.yml

@@ -0,0 +1,8 @@
+version: '2'
+services:
+  matomo:
+    scale: 1
+    start_on_create: true
+  matomo-db:
+    scale: 1
+    start_on_create: true

Sebastians/nextcloud/README.md

@@ -0,0 +1,13 @@
+Some Rancher v1.x organizational concepts have changed in racher v2.x:
+
+- environments -> projects
+- stacks -> namespaces 
+- services -> workloads
+
+To maintain same organization boundaries on rancher v2.x, is recommended to:
+
+- create a separated project for every rancher v1.x environment.
+- create a separated namespace for every rancher v1.x stack.
+
+Project: Sebastians
+Namespace: nextcloud

Sebastians/nextcloud/docker-compose.yml

@@ -0,0 +1,54 @@
+version: '2'
+services:
+  nextcloud:
+    image: nexus.sebastianfisahn.com/nextcloud:17.0.1
+    environment:
+      APC_SHM_SIZE: 256M
+      CRON_PERIOD: 15m
+      DB_HOST: nextcloud-db
+      DB_NAME: nextcloud
+      DB_PASSWORD: qT2QyZGcJ6KPfnph
+      DB_TYPE: mysql
+      DB_USER: nextcloud
+      DOMAIN: localhost
+      GID: '1000'
+      OPCACHE_MEM_SIZE: '256'
+      TZ: Europe/Berlin
+      UID: '1000'
+      UPLOAD_MAX_SIZE: 10G
+      REDIS_HOST: redis
+      REDIS_HOST_PORT: '6379'
+    volumes:
+    - /mnt/volume-data/nextcloud/data:/data
+    - /mnt/volume-data/nextcloud/config:/config
+    - /mnt/volume-data/nextcloud/apps:/apps2
+    - /mnt/volume-data/nextcloud/themes:/nextcloud/themes
+    - /mnt/volume-data/nextcloud/php-sessions:/php/session
+    domainname: nextcloud.sebastianfisahn.com
+    links:
+    - nextcloud-db:nextcloud-db
+    ports:
+    - 8888:8888/tcp
+    labels:
+      io.rancher.container.pull_image: always
+      wonderfall: nextcloud
+  nextcloud-db:
+    mem_limit: 262144000
+    image: mariadb:10
+    environment:
+      MYSQL_DATABASE: nextcloud
+      MYSQL_PASSWORD: qT2QyZGcJ6KPfnph
+      MYSQL_ROOT_PASSWORD: qT2QyZGcJ6KPfnph
+      MYSQL_USER: nextcloud
+    volumes:
+    - /mnt/volume-data/nextcloud/db:/var/lib/mysql
+    labels:
+      io.rancher.container.pull_image: always
+  redis:
+    image: redis:alpine
+    stdin_open: true
+    volumes:
+    - /mnt/volume-data/nextcloud/redis:/data
+    tty: true
+    labels:
+      io.rancher.container.pull_image: always

Sebastians/nextcloud/nextcloud-claim0-persistentvolumeclaim.yaml

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

Sebastians/nextcloud/nextcloud-claim1-persistentvolumeclaim.yaml

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

Sebastians/nextcloud/nextcloud-claim2-persistentvolumeclaim.yaml

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

Sebastians/nextcloud/nextcloud-claim3-persistentvolumeclaim.yaml

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

Sebastians/nextcloud/nextcloud-claim4-persistentvolumeclaim.yaml

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

Sebastians/nextcloud/nextcloud-db-claim0-persistentvolumeclaim.yaml

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

Sebastians/nextcloud/nextcloud-db-deployment.yaml

@@ -0,0 +1,46 @@
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+  creationTimestamp: null
+  labels:
+    io.kompose.service: nextcloud-db
+  name: nextcloud-db
+spec:
+  replicas: 0
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      creationTimestamp: null
+      labels:
+        io.kompose.service: nextcloud-db
+    spec:
+      containers:
+      - env:
+        - name: MYSQL_DATABASE
+          value: nextcloud
+        - name: MYSQL_PASSWORD
+          value: qT2QyZGcJ6KPfnph
+        - name: MYSQL_ROOT_PASSWORD
+          value: qT2QyZGcJ6KPfnph
+        - name: MYSQL_USER
+          value: nextcloud
+        image: mariadb:10
+        name: nextcloud-db
+        resources:
+          limits:
+            memory: 262144e3
+        volumeMounts:
+        - mountPath: /var/lib/mysql
+          name: nextcloud-db-claim0
+      restartPolicy: Always
+      volumes:
+      - name: nextcloud-db-claim0
+        persistentVolumeClaim:
+          claimName: nextcloud-db-claim0
+status: {}

Sebastians/nextcloud/nextcloud-deployment.yaml

@@ -0,0 +1,90 @@
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+    wonderfall: nextcloud
+  creationTimestamp: null
+  labels:
+    io.kompose.service: nextcloud
+  name: nextcloud
+spec:
+  replicas: 0
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      creationTimestamp: null
+      labels:
+        io.kompose.service: nextcloud
+    spec:
+      containers:
+      - env:
+        - name: APC_SHM_SIZE
+          value: 256M
+        - name: CRON_PERIOD
+          value: 15m
+        - name: DB_HOST
+          value: nextcloud-db
+        - name: DB_NAME
+          value: nextcloud
+        - name: DB_PASSWORD
+          value: qT2QyZGcJ6KPfnph
+        - name: DB_TYPE
+          value: mysql
+        - name: DB_USER
+          value: nextcloud
+        - name: DOMAIN
+          value: localhost
+        - name: GID
+          value: "1000"
+        - name: OPCACHE_MEM_SIZE
+          value: "256"
+        - name: REDIS_HOST
+          value: redis
+        - name: REDIS_HOST_PORT
+          value: "6379"
+        - name: TZ
+          value: Europe/Berlin
+        - name: UID
+          value: "1000"
+        - name: UPLOAD_MAX_SIZE
+          value: 10G
+        image: nexus.sebastianfisahn.com/nextcloud:17.0.1
+        name: nextcloud
+        ports:
+        - containerPort: 8888
+        resources: {}
+        volumeMounts:
+        - mountPath: /data
+          name: nextcloud-claim0
+        - mountPath: /config
+          name: nextcloud-claim1
+        - mountPath: /apps2
+          name: nextcloud-claim2
+        - mountPath: /nextcloud/themes
+          name: nextcloud-claim3
+        - mountPath: /php/session
+          name: nextcloud-claim4
+      restartPolicy: Always
+      subdomain: nextcloud.sebastianfisahn.com
+      volumes:
+      - name: nextcloud-claim0
+        persistentVolumeClaim:
+          claimName: nextcloud-claim0
+      - name: nextcloud-claim1
+        persistentVolumeClaim:
+          claimName: nextcloud-claim1
+      - name: nextcloud-claim2
+        persistentVolumeClaim:
+          claimName: nextcloud-claim2
+      - name: nextcloud-claim3
+        persistentVolumeClaim:
+          claimName: nextcloud-claim3
+      - name: nextcloud-claim4
+        persistentVolumeClaim:
+          claimName: nextcloud-claim4
+status: {}

Sebastians/nextcloud/nextcloud-service.yaml

@@ -0,0 +1,22 @@
+apiVersion: v1
+kind: Service
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+    wonderfall: nextcloud
+  creationTimestamp: null
+  labels:
+    io.kompose.service: nextcloud
+  name: nextcloud
+spec:
+  ports:
+  - name: "8888"
+    port: 8888
+    targetPort: 8888
+  selector:
+    io.kompose.service: nextcloud
+status:
+  loadBalancer: {}

Sebastians/nextcloud/output.txt

@@ -0,0 +1,33 @@
+## This is the service-wise list of constructs that need to be handled specially.
+Please refer https://rancher.com/docs/rancher/v2.x/en/v1.6-migration/ to transition these to Rancher 2.0.
+nextcloud:
+  labels:
+    >>io.rancher.container.pull_image
+    >>wonderfall
+  links:
+    Refer: https://rancher.com/blog/2018/2018-09-04-service_discovery_2dot0/
+    Please add the necessary Service Discovery Records for your Rancher 2.0 Kubernetes workload to implement the links.
+  ports:
+    Refer: https://rancher.com/blog/2018/2018-08-14-expose-and-monitor-workloads/
+    Please add a hostPort or a nodePort to your Kubernetes workload to expose the ports used.
+  scale:
+  start_on_create:
+  volumes:
+nextcloud-db:
+  labels:
+    >>io.rancher.container.pull_image
+  scale:
+  start_on_create:
+  volumes:
+redis:
+  labels:
+    >>io.rancher.container.pull_image
+  scale:
+  start_on_create:
+  volumes:
+
+## More Docker/Rancher1.6 constructs that need to be transitioned to Kubernetes/Rancher 2.0 in a special way:
+  Rancher Metadata - Incase your applications depend on metadata.
+  Rancher 1.6 FQDN resolution format
+
+Please contact Rancher Support for more help to migrate these to Rancher 2.0, as there is no direct translation available.

Sebastians/nextcloud/rancher-compose.yml

@@ -0,0 +1,11 @@
+version: '2'
+services:
+  nextcloud:
+    scale: 1
+    start_on_create: true
+  nextcloud-db:
+    scale: 1
+    start_on_create: true
+  redis:
+    scale: 1
+    start_on_create: true

Sebastians/nextcloud/redis-claim0-persistentvolumeclaim.yaml

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

Sebastians/nextcloud/redis-deployment.yaml

@@ -0,0 +1,37 @@
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+  creationTimestamp: null
+  labels:
+    io.kompose.service: redis
+  name: redis
+spec:
+  replicas: 0
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      creationTimestamp: null
+      labels:
+        io.kompose.service: redis
+    spec:
+      containers:
+      - image: redis:alpine
+        name: redis
+        resources: {}
+        stdin: true
+        tty: true
+        volumeMounts:
+        - mountPath: /data
+          name: redis-claim0
+      restartPolicy: Always
+      volumes:
+      - name: redis-claim0
+        persistentVolumeClaim:
+          claimName: redis-claim0
+status: {}

Sebastians/rancher migration.txt

@@ -0,0 +1,11 @@
+migration-tools export --url https://rancher.sebastianfisahn.com --access-key 6AC75D5207AAE8DCDCE8 --secret-key CdwVDCCjNRKzJ1q3spRyFerzg6zvck9RXnf4NaK7 --export-dir /rancher-files --all
+
+6AC75D5207AAE8DCDCE8 (access key)
+
+CdwVDCCjNRKzJ1q3spRyFerzg6zvck9RXnf4NaK7 (secret)
+
+
+migration-tools parse --docker-file docker-compose.yml --rancher-file rancher-compose.yml
+
+
+proxy_pass http://172.17.0.1:81/;

Sebastians/wordpress/README.md

@@ -0,0 +1,13 @@
+Some Rancher v1.x organizational concepts have changed in racher v2.x:
+
+- environments -> projects
+- stacks -> namespaces 
+- services -> workloads
+
+To maintain same organization boundaries on rancher v2.x, is recommended to:
+
+- create a separated project for every rancher v1.x environment.
+- create a separated namespace for every rancher v1.x stack.
+
+Project: Sebastians
+Namespace: wordpress

Sebastians/wordpress/db-claim0-persistentvolumeclaim.yaml

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

Sebastians/wordpress/db-deployment.yaml

@@ -0,0 +1,40 @@
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+  creationTimestamp: null
+  labels:
+    io.kompose.service: db
+  name: db
+spec:
+  replicas: 0
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      creationTimestamp: null
+      labels:
+        io.kompose.service: db
+    spec:
+      containers:
+      - env:
+        - name: MYSQL_ROOT_PASSWORD
+          value: example
+        image: mariadb
+        name: db
+        resources: {}
+        securityContext:
+          privileged: true
+        volumeMounts:
+        - mountPath: /var/lib/mysql
+          name: db-claim0
+      restartPolicy: Always
+      volumes:
+      - name: db-claim0
+        persistentVolumeClaim:
+          claimName: db-claim0
+status: {}

Sebastians/wordpress/docker-compose.yml

@@ -0,0 +1,21 @@
+version: '2'
+services:
+  wordpress:
+    image: wordpress
+    volumes:
+    - /mnt/volume-data/wordpress:/var/www/html
+    links:
+    - db:mysql
+    ports:
+    - 81:80/tcp
+    labels:
+      io.rancher.container.pull_image: always
+  db:
+    privileged: true
+    image: mariadb
+    environment:
+      MYSQL_ROOT_PASSWORD: example
+    volumes:
+    - /mnt/volume-data/wordpress-database:/var/lib/mysql
+    labels:
+      io.rancher.container.pull_image: always

Sebastians/wordpress/output.txt

@@ -0,0 +1,26 @@
+## This is the service-wise list of constructs that need to be handled specially.
+Please refer https://rancher.com/docs/rancher/v2.x/en/v1.6-migration/ to transition these to Rancher 2.0.
+db:
+  labels:
+    >>io.rancher.container.pull_image
+  scale:
+  start_on_create:
+  volumes:
+wordpress:
+  labels:
+    >>io.rancher.container.pull_image
+  links:
+    Refer: https://rancher.com/blog/2018/2018-09-04-service_discovery_2dot0/
+    Please add the necessary Service Discovery Records for your Rancher 2.0 Kubernetes workload to implement the links.
+  ports:
+    Refer: https://rancher.com/blog/2018/2018-08-14-expose-and-monitor-workloads/
+    Please add a hostPort or a nodePort to your Kubernetes workload to expose the ports used.
+  scale:
+  start_on_create:
+  volumes:
+
+## More Docker/Rancher1.6 constructs that need to be transitioned to Kubernetes/Rancher 2.0 in a special way:
+  Rancher Metadata - Incase your applications depend on metadata.
+  Rancher 1.6 FQDN resolution format
+
+Please contact Rancher Support for more help to migrate these to Rancher 2.0, as there is no direct translation available.

Sebastians/wordpress/rancher-compose.yml

@@ -0,0 +1,8 @@
+version: '2'
+services:
+  wordpress:
+    scale: 1
+    start_on_create: true
+  db:
+    scale: 1
+    start_on_create: true

Sebastians/wordpress/wordpress-claim0-persistentvolumeclaim.yaml

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

Sebastians/wordpress/wordpress-deployment.yaml

@@ -0,0 +1,39 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+  creationTimestamp: null
+  labels:
+    io.kompose.service: wordpress
+  name: wordpress
+spec:
+  replicas: 1
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      creationTimestamp: null
+      labels:
+        io.kompose.service: wordpress
+      selector: 
+        io.kompose.service: wordpress
+    spec:
+      containers:
+      - image: wordpress
+        name: wordpress
+        ports:
+        - containerPort: 80
+        resources: {}
+        volumeMounts:
+        - mountPath: /var/www/html
+          name: wordpress-claim0
+      restartPolicy: Always
+      volumes:
+      - name: wordpress-claim0
+        persistentVolumeClaim:
+          claimName: wordpress-claim0
+status: {}

Sebastians/wordpress/wordpress-service.yaml

@@ -0,0 +1,21 @@
+apiVersion: apps/v1beta1
+kind: Service
+metadata:
+  annotations:
+    io.rancher.container.pull_image: always
+    kompose.cmd: migration-tools parse --docker-file docker-compose.yml --rancher-file
+      rancher-compose.yml
+    kompose.version: 1.16.0 (HEAD)
+  creationTimestamp: null
+  labels:
+    io.kompose.service: wordpress
+  name: wordpress
+spec:
+  ports:
+  - name: "81"
+    port: 81
+    targetPort: 80
+  selector:
+    io.kompose.service: wordpress
+status:
+  loadBalancer: {}