Remove namespace (apache-spark-on-k8s#7)

* Remove namespace specifications * Removing namespace from helm chart * Remove readme refs * Revert readme change
a140262 · Apr 27, 2017 · 8dd3d95 · 8dd3d95
1 parent b40fc37
commit 8dd3d95
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 15 deletions.
diff --git a/charts/hdfs-datanode-k8s/README.md b/charts/hdfs-datanode-k8s/README.md
@@ -29,16 +29,16 @@ HDFS `datanodes` running inside a kubernetes cluster. See the other chart for
      of them below in --set as comma-separated entries)
 
   ```
-  $ helm install -n my-hdfs-datanode --namespace kube-system  \
+  $ helm install -n my-hdfs-datanode \
       --set clusterDnsIP=YOUR-KUBE-DNS-IP hdfs-datanode-k8s
   ```
 
   5. Confirm the daemons are launched.
 
   ```
-  $ kubectl get pods --all-namespaces | grep hdfs-datanode-
-  kube-system   hdfs-datanode-ajdcz 1/1 Running 0 7m
-  kube-system   hdfs-datanode-f1w24 1/1 Running 0 7m
+  $ kubectl get pods | grep hdfs-datanode-
+  hdfs-datanode-ajdcz 1/1 Running 0 7m
+  hdfs-datanode-f1w24 1/1 Running 0 7m
   ```
 
 `Datanode` daemons run on every cluster node. They also mount k8s `hostPath`
@@ -47,7 +47,7 @@ local disk volumes.
 `Datanodes` are using `hostNetwork` to register to `namenode` using
 physical IPs.
 
-Note they run under the `kube-system` namespace.
+Note they run under the `default` namespace.
 
 ###Credits
 

diff --git a/charts/hdfs-datanode-k8s/templates/datanode-daemonset.yaml b/charts/hdfs-datanode-k8s/templates/datanode-daemonset.yaml
@@ -16,7 +16,6 @@ apiVersion: v1
 kind: ConfigMap
 metadata:
   name: resolv-conf-datanode
-  namespace: kube-system
 data:
   resolv.conf: |
     search kube-system.svc.{{ .Values.clusterDomain }} svc.{{ .Values.clusterDomain }} {{ .Values.clusterDomain }}
@@ -29,7 +28,6 @@ apiVersion: extensions/v1beta1
 kind: DaemonSet
 metadata:
   name: hdfs-datanode
-  namespace: kube-system
 spec:
   template:
     metadata:

diff --git a/charts/hdfs-namenode-k8s/README.md b/charts/hdfs-namenode-k8s/README.md
@@ -20,14 +20,14 @@ HDFS `namenode` running inside a kubernetes cluster. See the other chart for
   2. Launch this helm chart, `hdfs-namenode-k8s`.
 
   ```
-  $ helm install -n my-hdfs-namenode --namespace kube-system hdfs-k8s
+  $ helm install -n my-hdfs-namenode hdfs-k8s
   ```
 
   3. Confirm the daemon is launched.
 
   ```
-  $ kubectl get pods --all-namespaces | grep hdfs-namenode
-  kube-system   hdfs-namenode-0 1/1 Running   0 7m
+  $ kubectl get pods | grep hdfs-namenode
+  hdfs-namenode-0 1/1 Running   0 7m
   ```
 
 There will be only one `namenode` instance. i.e. High Availability (HA) is not
@@ -38,8 +38,6 @@ mount a local disk directory using k8s `hostPath` volume.
 `namenode` is using `hostNetwork` so it can see physical IPs of datanodes
 without an overlay network such as weave-net mask them.
 
-Note it runs under the `kube-system` namespace.
-
 ###Credits
 
 This chart is using public Hadoop docker images hosted by

diff --git a/charts/hdfs-namenode-k8s/templates/namenode-statefulset.yaml b/charts/hdfs-namenode-k8s/templates/namenode-statefulset.yaml
@@ -18,7 +18,6 @@ apiVersion: v1
 kind: Service
 metadata:
   name: hdfs-namenode
-  namespace: kube-system
   labels:
     app: hdfs-namenode
 spec:
@@ -33,7 +32,6 @@ apiVersion: apps/v1beta1
 kind: StatefulSet
 metadata:
   name: hdfs-namenode
-  namespace: kube-system
 spec:
   serviceName: "hdfs-namenode"
   # Create a size-1 set. The namenode DNS name will be
@@ -48,7 +46,6 @@ spec:
       # like weave. Otherwise, namenode fails to see physical IP address of datanodes.
       hostNetwork: true
       hostPID: true
-      terminationGracePeriodSeconds: 0
       containers:
         - name: hdfs-namenode
           image: uhopper/hadoop-namenode:2.7.2