minor style and typo fixes

Dockerfile

@@ -15,8 +15,8 @@ LABEL org.label-schema.vcs-ref=$VCS_REF \
 ENV KUBE_LATEST_VERSION="v1.24.0"
 
 RUN apk add --update --no-cache ca-certificates=20211220-r0 curl=7.80.0-r1 jq=1.6-r1 \
- && curl -L https://storage.googleapis.com/kubernetes-release/release/${KUBE_LATEST_VERSION}/bin/linux/$TARGETARCH/kubectl -o /usr/local/bin/kubectl \
- && chmod +x /usr/local/bin/kubectl
+    && curl -L https://storage.googleapis.com/kubernetes-release/release/${KUBE_LATEST_VERSION}/bin/linux/$TARGETARCH/kubectl -o /usr/local/bin/kubectl \
+    && chmod +x /usr/local/bin/kubectl
 
 ADD wait_for.sh /usr/local/bin/wait_for.sh
 

README.md

@@ -113,8 +113,8 @@ spec:
 
 This container is used extensively in deployments of Onedata system [onedata/charts](https://github.com/onedata/charts) to specify dependencies. It leverages Kubernetes [init containers](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/), thus providing:
 
-  - a detailed event log in `kubectl describe <pod>`, on what init container is pod hanging at the moment.
-  - a comprehensive view in `kubectl get pods` output where init containers are shown in a form `Init:<ready>/<total>`
+    - a detailed event log in `kubectl describe <pod>`, on what init container is pod hanging at the moment.
+    - a comprehensive view in `kubectl get pods` output where init containers are shown in a form `Init:<ready>/<total>`
 
 Example output from the deployment run of ~16 pod with dependencies just after deployment:
 
@@ -191,21 +191,21 @@ develop-volume-s3-krakow-23786741-pdxtj                1/1       Running
 develop-volume-s3-lisbon-3912793669-d4xh5              1/1       Running           0          59s
 develop-volume-s3-paris-124394749-qwt18                1/1       Running           0          57s
 ```
-## Troubleshooting
 
-Verify that you can access the Kubernetes API from within the k8s-wait-for container by running `kubectl get services`. If you get a permissions error like   
+## Troubleshooting
 
-`Error from server (Forbidden): services is forbidden: User "system:serviceaccount:default:default" cannot list resource "services" in API group "" in the namespace "default"`   
+Verify that you can access the Kubernetes API from within the k8s-wait-for container by running `kubectl get services`. If you get a permissions error like
 
-the pod lacks the permissions to perform the `kubectl get` query. To fix this, follow the instrctions for the 'pod-reader' role and clusterrole at   
+`Error from server (Forbidden): services is forbidden: User "system:serviceaccount:default:default" cannot list resource "services" in API group "" in the namespace "default"`
 
-https://kubernetes.io/docs/reference/access-authn-authz/rbac/#kubectl-create-role
+the pod lacks the permissions to perform the `kubectl get` query. To fix this, follow the instrctions for the 'pod-reader' role and clusterrole [here](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#kubectl-create-role
+).
 
-or use these command lines which add services and deployments to the pods in those examples:      
-`kubectl create role pod-reader --verb=get --verb=list --verb=watch --resource=pods,services,deployments`   
+or use these command lines which add services and deployments to the pods in those examples:
+`kubectl create role pod-reader --verb=get --verb=list --verb=watch --resource=pods,services,deployments`
 
 `kubectl create rolebinding default-pod-reader --role=pod-reader --serviceaccount=default:default --namespace=default`
 
-An extensive discussion on the problem of granting necessary permisions and a number of example solutions can be found [here](https://github.com/groundnuty/k8s-wait-for/issues/6).
+An extensive discussion on the problem of granting necessary permissions and a number of example solutions can be found [here](https://github.com/groundnuty/k8s-wait-for/issues/6).
 
-Make sure the service account is mounted. `The connection to the server localhost:8080 was refused - did you specify the right host or port?` might indicate that the service account is not mounted to the pod. Double check wether your service account and pod define `automountServiceAccountToken: true`. If the service account is mounted, you should see files inside `/var/run/secrets/kubernetes.io/serviceaccount` folder, otherwise `/var/run/secrets/kubernetes.io` might not exist at all.
+Make sure the service account is mounted. `The connection to the server localhost:8080 was refused - did you specify the right host or port?` might indicate that the service account is not mounted to the pod. Double check whether your service account and pod define `automountServiceAccountToken: true`. If the service account is mounted, you should see files inside `/var/run/secrets/kubernetes.io/serviceaccount` folder, otherwise `/var/run/secrets/kubernetes.io` might not exist at all.

evaluate_platform.sh

@@ -16,8 +16,8 @@ else
 fi
 
 if [ -z $PLATFORM ]; then 
-  echo "Platform could not be detected, aborting...";
-  exit 1
+    echo "Platform could not be detected, aborting...";
+    exit 1
 fi
 
 echo "linux/$PLATFORM"

wait_for.sh

@@ -10,7 +10,7 @@ TOP_PID=$$
 KUBECTL_ARGS=""
 WAIT_TIME="${WAIT_TIME:-2}" # seconds
 DEBUG="${DEBUG:-0}"
-TREAT_ERRORS_AS_READY=0
+TREAT_ERRORS_AS_READY="${TREAT_ERRORS_AS_READY:-0}"
 
 usage() {
 cat <<EOF