This is an automated email from the ASF dual-hosted git repository.
rabbah pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/openwhisk-deploy-kube.git
The following commit(s) were added to refs/heads/master by this push:
new ec240ee chore: fix spelling (#680)
ec240ee is described below
commit ec240eeae11ad93b449a54e5995beee1fa3977e7
Author: John Bampton <[email protected]>
AuthorDate: Wed Mar 10 02:24:39 2021 +1000
chore: fix spelling (#680)
---
README.md | 8 ++++----
docs/configurationChoices.md | 4 ++--
docs/k8s-ibm-private.md | 2 +-
docs/okd-311.md | 2 +-
docs/private-docker-registry.md | 2 +-
helm/openwhisk/README.md | 2 +-
helm/openwhisk/configMapFiles/tests/smoketest/myTask.sh | 4 ++--
helm/openwhisk/templates/_affinity.tpl | 2 +-
helm/openwhisk/values.schema.json | 4 ++--
9 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/README.md b/README.md
index 7eb1dab..6ecf02d 100644
--- a/README.md
+++ b/README.md
@@ -243,7 +243,7 @@ For simplicity, in this README, we have used `owdev` as the
release name and
You can use a different name and/or namespace simply by changing the commands
used below.
-**NOTE:** The commands below assume Helm v3.2.0 or higher. Verfiy your local
Helm version with the command `helm version`.
+**NOTE:** The commands below assume Helm v3.2.0 or higher. Verify your local
Helm version with the command `helm version`.
### Deploying Released Charts from Helm Repository
@@ -261,7 +261,7 @@ helm install owdev openwhisk/openwhisk -n openwhisk
--create-namespace -f myclus
To deploy directly from sources, either download the
[latest source
release](https://github.com/apache/openwhisk-deploy-kube/releases) or
`git clone https://github.com/apache/openwhisk-deploy-kube.git` and use the
Helm chart
-from the `helm/openwhisk` folder of the sourc tree.
+from the `helm/openwhisk` folder of the source tree.
```shell
helm install owdev ./helm/openwhisk -n openwhisk --create-namespace -f
mycluster.yaml
@@ -409,7 +409,7 @@ controller:
### Selectively redeploying using a locally built docker image
You can use the `helm upgrade` command to selectively redeploy one or
-more OpenWhisk componenets. Continuing the example above, if you make
+more OpenWhisk components. Continuing the example above, if you make
additional changes to the controller source code and want to just
redeploy it without redeploying the entire OpenWhisk system you can do
the following:
@@ -424,7 +424,7 @@ controller:
imageName: "whisk/controller"
imageTag: "v2"
```
-Redeploy with Helm by executing this commaned in your
+Redeploy with Helm by executing this command in your
openwhisk-deploy-kube directory:
```shell
helm upgrade owdev ./helm/openwhisk -n openwhisk -f mycluster.yaml
diff --git a/docs/configurationChoices.md b/docs/configurationChoices.md
index 7a7950e..9244fab 100644
--- a/docs/configurationChoices.md
+++ b/docs/configurationChoices.md
@@ -40,7 +40,7 @@ NOTE: setting the replicaCount to be greater than 1 for the
following
components is not currently supported:
- apigateway and redis. Running only a single replica of these services is
unlikely to be a significant scalability bottleneck.
-- couchdb. For production deployments of OpenWhisk on Kubernetes, we strongly
recomend running
+- couchdb. For production deployments of OpenWhisk on Kubernetes, we strongly
recommend running
CouchDB externally to OpenWhisk as described below. An external CouchDB
instance enables
better management of the database and decouples its lifecycle from that of
the OpenWhisk deployment.
- The event providers: alarmprovider and kafkaprovider.
@@ -152,7 +152,7 @@ be scheduled. If your Kubernetes cluster is properly
configured to support
including having a DefaultStorageClass admission controller and a
designated default StorageClass, then this will all happen seamlessly.
-See [NFS Dynamis Storage Provisioning](./k8s-nfs-dynamic-storage.md) for one
+See [NFS Dynamic Storage Provisioning](./k8s-nfs-dynamic-storage.md) for one
approach to provisioning dynamic storage if it's not already provisioned
on your cluster.
diff --git a/docs/k8s-ibm-private.md b/docs/k8s-ibm-private.md
index 21c12fc..7c677fb 100644
--- a/docs/k8s-ibm-private.md
+++ b/docs/k8s-ibm-private.md
@@ -42,7 +42,7 @@ or be prepared to provision volumes manually for OpenWhisk
IBM Cloud Private includes a provision for filtering the images that are
allowed to be deployed into a particular namespace. One _could_ disable this
-capability for the OpenWhisk namespace, but initally it is best to define
+capability for the OpenWhisk namespace, but initially it is best to define
a policy for the namespace: (In this case we assume the namespace is
`openwhisk`)
diff --git a/docs/okd-311.md b/docs/okd-311.md
index a8ba7fe..dfd1b8c 100644
--- a/docs/okd-311.md
+++ b/docs/okd-311.md
@@ -25,7 +25,7 @@ The 3.11 version of OKD/OpenShift is based on Kubernetes 1.11.
We assume you have an operational cluster that meets the
[technical requirements](okd-technical-requirements.md) and that you
-have sufficient priveleges to perform the necessary `oc adm`
+have sufficient privileges to perform the necessary `oc adm`
operations detailed below.
## Initial Setup
diff --git a/docs/private-docker-registry.md b/docs/private-docker-registry.md
index 69ffbc2..245b5dc 100644
--- a/docs/private-docker-registry.md
+++ b/docs/private-docker-registry.md
@@ -42,7 +42,7 @@ By default, helm charts currently use docker hub to download
images to deploy Op
registry:
name: "registry-name/"
username: username
- password: "Passowrd"
+ password: "Password"
```
> - enabling registry information will cause all your images to be pulled
from private docker registry only.
diff --git a/helm/openwhisk/README.md b/helm/openwhisk/README.md
index 1e6e867..80d46a5 100644
--- a/helm/openwhisk/README.md
+++ b/helm/openwhisk/README.md
@@ -38,7 +38,7 @@ In its default configuration, this chart will create the
following Kubernetes re
* apigateway, controller, couchdb, kafka, nginx, redis, zookeeper
* OpenWhisk control plane Pods:
* Deployments: apigateway, couchdb, nginx, redis
- * SatefulSets: controller, invoker, kafka, zookeeper
+ * StatefulSets: controller, invoker, kafka, zookeeper
* Persistent Volume Claims
* couchdb-pvc
* kafka-pvc
diff --git a/helm/openwhisk/configMapFiles/tests/smoketest/myTask.sh
b/helm/openwhisk/configMapFiles/tests/smoketest/myTask.sh
index d599f4a..ed3d764 100644
--- a/helm/openwhisk/configMapFiles/tests/smoketest/myTask.sh
+++ b/helm/openwhisk/configMapFiles/tests/smoketest/myTask.sh
@@ -52,7 +52,7 @@ until $ACTION_LIST_PASSED; do
done
# next invoke the new hello world action via the CLI
-echo "Inoking action via CLI"
+echo "Invoking action via CLI"
RESULT=$(wsk -i action invoke --blocking hello | grep "\"status\":
\"success\"")
if [ -z "$RESULT" ]; then
echo "FAILED! Could not invoke hello action via CLI"
@@ -79,7 +79,7 @@ if [ -z "$RESULT" ]; then
exit 1
fi
-# now delete the resouces so the test could be run again
+# now delete the resources so the test could be run again
wsk -i api delete /demo || (echo "FAILED! failed to delete API"; exit 1)
wsk -i action delete hello || (echo "FAILED! failed to delete action"; exit 1)
diff --git a/helm/openwhisk/templates/_affinity.tpl
b/helm/openwhisk/templates/_affinity.tpl
index ba0e4de..61ebbcc 100644
--- a/helm/openwhisk/templates/_affinity.tpl
+++ b/helm/openwhisk/templates/_affinity.tpl
@@ -61,7 +61,7 @@ nodeAffinity:
{{- end -}}
-{{/* Generic provder affinity */}}
+{{/* Generic provider affinity */}}
{{- define "openwhisk.affinity.provider" -}}
# prefer to not run on an invoker node (only prefer because of single node
clusters)
nodeAffinity:
diff --git a/helm/openwhisk/values.schema.json
b/helm/openwhisk/values.schema.json
index 288e0ed..fba7630 100644
--- a/helm/openwhisk/values.schema.json
+++ b/helm/openwhisk/values.schema.json
@@ -139,8 +139,8 @@
"limits": {
"type": "object",
"properties": {
- "actionsInvokesPerminute": { "type": "number", "minimum": 0,
"descrption": "The maximum number of action invocations per minute by a single
namespace" },
- "actionsInvokesConcurrent": { "type": "number", "minimum": 0,
"descrption": "The maximum number of concurrent action invocations by a single
namespace" },
+ "actionsInvokesPerminute": { "type": "number", "minimum": 0,
"description": "The maximum number of action invocations per minute by a single
namespace" },
+ "actionsInvokesConcurrent": { "type": "number", "minimum": 0,
"description": "The maximum number of concurrent action invocations by a
single namespace" },
"triggersFiresPerminute": { "type": "number", "minimum": 0,
"description": "The maximum triggers fired per minute for a single namespace" },
"actionsSequenceMaxLength": { "type": "number", "minimum": 0,
"description": "The maximum length of an action sequence" },
"actions": {
