$ helm install --name hdtest --namespace hdns hdfs
NAME: hdtest
LAST DEPLOYED: Wed Jul 31 15:42:53 2019
NAMESPACE: hdns
STATUS: DEPLOYED
RESOURCES:
==> v1/ConfigMap
NAME DATA AGE
hdtest-hdfs 4 0s
==> v1/Pod(related)
NAME READY STATUS RESTARTS AGE
hdtest-hdfs-hdfs-dn-0 0/1 ContainerCreating 0 0s
hdtest-hdfs-hdfs-nn-0 0/1 ContainerCreating 0 0s
==> v1/Service
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
hdtest-hdfs-hdfs-dn ClusterIP None <none> 9000/TCP,50075/TCP 0s
hdtest-hdfs-hdfs-nn ClusterIP None <none> 9000/TCP,50070/TCP 0s
==> v1beta1/PodDisruptionBudget
NAME MIN AVAILABLE MAX UNAVAILABLE ALLOWED DISRUPTIONS AGE
hdtest-hdfs-hdfs-dn 1 N/A 0 0s
hdtest-hdfs-hdfs-nn 1 N/A 0 0s
==> v1beta1/StatefulSet
NAME READY AGE
hdtest-hdfs-hdfs-dn 0/1 0s
hdtest-hdfs-hdfs-nn 0/1 0s
NOTES:
1. You can check the status of HDFS by running this command:
kubectl exec -n hdns -it hdtest-hdfs-hdfs-nn-0 -- /usr/local/hadoop/bin/hdfs dfsadmin -report
$ kubectl exec -n hdns -it hdtest-hdfs-hdfs-nn-0 -- /usr/local/hadoop/bin/hdfs dfsadmin -report
report: java.net.UnknownHostException: hdtest-hdfs-hdfs-nn
Usage: hdfs dfsadmin [-report] [-live] [-dead] [-decommissioning]
command terminated with exit code 255