@@ -105,12 +105,17 @@ chart](develop-helm-chart).
105105
106106## Develop Kubernetes integration
107107
108+ ``` {important}
108109This requires `helm` and a functional Kubernetes cluster. Please do
109110[preliminary Kubernetes setup](kubernetes-setup) if you haven't already
110111before continuing here.
112+ ```
111113
112- With a Kubernetes cluster running, as you verify with ` kubectl version ` , you can
113- continue.
114+ 1 . Verify that you have access to a Kubernetes cluster running.
115+
116+ ``` bash
117+ kubectl version
118+ ```
114119
1151201 . Locally install BinderHub as a Python package and its development
116121 requirements locally.
@@ -131,7 +136,9 @@ continue.
131136
1321371 . Configure ` docker ` using environment variables to use the same Docker daemon
133138 as your local Kubernetes cluster. This means images you build are directly
134- available to the cluster. If using ` minikube ` ,
139+ available to the cluster.
140+
141+ If using ` minikube ` ,
135142
136143 ``` bash
137144 eval $( minikube docker-env)
@@ -151,10 +158,10 @@ continue.
151158
1521591 . Visit [ http://localhost:8585 ] ( http://localhost:8585 )
153160
154- 1 . Congratulations, you can now make changes and see how they influence the
155- deployment. You may be required to restart the BinderHub depending on what
156- you change. You can also start running ` pytest ` tests to verify the
157- Deployment functions as it should.
161+ Congratulations, you can now make changes and see how they influence the
162+ deployment. You may be required to restart the BinderHub depending on what
163+ you change. You can also start running ` pytest ` tests to verify the
164+ Deployment functions as it should.
158165
159166### Cleanup resources
160167
0 commit comments