Skip to content

Commit 1229c32

Browse files
authored
docs: Removed ref to unused kind (#5183)
removed ref to unused kind Signed-off-by: dandawg <12484302+dandawg@users.noreply.github.com>
1 parent 0083303 commit 1229c32

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

examples/operator-quickstart/01-Install.ipynb

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
"# Install Feast on Kubernetes with the Feast Operator\n",
88
"## Objective\n",
99
"\n",
10-
"Provide a reference implementation of a runbook to deploy a Feast environment on a Kubernetes cluster using [Kind](https://kind.sigs.k8s.io/docs/user/quick-start) and the [Feast Operator](../../infra/feast-operator/)."
10+
"Provide a reference implementation of a runbook to deploy a Feast environment on a Kubernetes cluster using the [Feast Operator](../../infra/feast-operator/)."
1111
]
1212
},
1313
{
@@ -87,15 +87,15 @@
8787
"metadata": {},
8888
"source": [
8989
"## Deployment Architecture\n",
90-
"The primary objective of this runbook is to guide the deployment of Feast services on a Kubernetes Kind cluster, using the `postgres` template to set up a basic feature store.\n",
90+
"The primary objective of this runbook is to guide the deployment of Feast services on a Kubernetes cluster, using the `postgres` template to set up a basic feature store.\n",
9191
"\n",
9292
"In this notebook, we will deploy a distributed topology of Feast services, which includes:\n",
9393
"\n",
9494
"* `Registry Server`: Handles metadata storage for feature definitions.\n",
9595
"* `Online Store Server`: Uses the `Registry Server` to query metadata and is responsible for low-latency serving of features.\n",
9696
"* `Offline Store Server`: Uses the `Registry Server` to query metadata and provides access to batch data for historical feature retrieval.\n",
9797
"\n",
98-
"Each service is backed by a `PostgreSQL` database, which is also deployed within the same Kind cluster."
98+
"Each service is backed by a `PostgreSQL` database, which is also deployed within the same cluster."
9999
]
100100
},
101101
{

0 commit comments

Comments
 (0)