Update README.md

Author: Mantene

README.md

@@ -34,8 +34,7 @@ CMD vncserver && websockify -D --web=/usr/share/novnc/ --cert=~/novnc.pem 80 loc
 
 ````
 
-1. Replace the COPY keen /dos/keen with your game (ie. COPY wolf3d /dos/wolf3d). 1. You can also change the default password, or override it with a -e parameter when you run the image.
-1. Now, with Docker, build the image. I’m assuming you already have Docker installed and are familiar with it to some extent. CD to the directory in a console and run the command…
+1. Build the image. I’m assuming you already have Docker installed and are familiar with it to some extent. CD to the directory in a console and run the command…
   ````
   docker build -t mydosbox .
   ````
@@ -45,56 +44,6 @@ CMD vncserver && websockify -D --web=/usr/share/novnc/ --cert=~/novnc.pem 80 loc
    ````
 
 1. Open a browser and point it to http://localhost:6080/vnc.html
-1. You should see a prompt for the password. Type it in, and you should be able to connect to your container with DosBox running. The game is started automatically.
+1. You should see a prompt for the password. Type it in, and you should be able to connect to your container with DosBox running.
 1. Once your image is built, you can push it to your image repository with docker push, but you’ll need to tag it appropriately.
 
-# USE WITH KUBERNETES
-Kubernetes is another part of the equation when it comes to container apps. Containers on Kubernetes are deployed into pods, which are then usually a part of a part of a deployment, which will have one or more pods associated with it. Deployments can also be used for creating scalable sets of pods for high availability too on a Kubernetes cluster. If you’re not familiar with Kubernetes, check out this webinar below where I go in depth on the matter.
-
-Deployments and services can be defined declaratively with a YAML file. Below is a Kuberenetes YAML file that defines a deployment and a service for my retro gaming container.
-
-The deployment is simple – it points to a single container image called blaize/keen and then tells Kubernetes what ports to expose for the container. The service defines how the deployment will be exposed on a network. In this case, it’s using a TCP load balancer, where it is exposing port 80 and mapping that to the port exposed by the deployment. The service uses selectors on the label app to match the service with the deployment.
-
-````
-apiVersion: v1
-kind: Service
-metadata:
-  name: keen-service
-  labels:
-    app: keen-deployment
-spec:
-  ports:
-  - port: 80
-    targetPort: 6080
-  selector:
-    app: keen-deployment
-  type: LoadBalancer
----
-apiVersion: apps/v1 
-kind: Deployment
-metadata:
-  name: keen-deployment
-spec:
-  selector:
-    matchLabels:
-      app: keen-deployment
-  replicas: 1
-  template:
-    metadata:
-      labels:
-        app: keen-deployment
-    spec:
-      containers:
-      - name: master
-        image: blaize/keen
-        ports:
-        - containerPort: 80
-````
-
-To connect use this, first create a file called keen.yaml file, configure your instance kubectl to work with your instance of Kubernetes, then run deploy the sample.
-
-````
-kubectl create -f keen.yaml
-````
-
-When this is deployed to Kubernetes, Kubernetes will configure the external network to open on port 80 to listen to incoming requests. When used on Azure Kubernetes Services, AKS will create and map a public IP address (htttp://[your ip address]/vnc.html) for the service. Once connected, you can point your browser to the IP address of your cluster and have fun playing your retro games!