@@ -61,7 +61,7 @@ There are two modes on the Actions button:
6161In this chapter, we focus on utilizing the first option to provide a comprehensive view of the deployment process.
6262
6363<a href = { action } >
64- <img src = { action } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
64+ <img src = { action } className = " chapter-image " />
6565</a >
6666
6767<h2 class = " chapter-sub-heading" >Design Validation</h2 >
@@ -85,15 +85,15 @@ This comprehensive validation ensures that:
85851 . Click on the ** Validate** Icon.
8686
8787 <a href = { performingValidation } >
88- <img src = { performingValidation } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
88+ <img src = { performingValidation } className = " chapter-image " />
8989 </a >
9090
9191 If the validation is successful, you will see a modal displaying the number of components validated and the number of annotations, similar to the one shown below:
9292
9393
9494
9595 <a href = { successfulValidation } >
96- <img src = { successfulValidation } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
96+ <img src = { successfulValidation } className = " chapter-image " />
9797 </a >
9898
9999<h3 class = " chapter-sub-heading" >Handling Validation Errors</h3 >
@@ -107,7 +107,7 @@ A common validation error is:
1071071 . ** Missing Required Field** : This happens when a required field is not provided. For example, in the image below, the first error indicates that the field ".spec.template.spec.containers.0.env.0" must have a value.
108108
109109 <a href = { validationError } >
110- <img src = { validationError } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
110+ <img src = { validationError } className = " chapter-image " />
111111 </a >
112112
113113To troubleshoot and remediate validation issues:
@@ -132,7 +132,7 @@ A dry run in Meshery simulates the deployment of your design in the selected tar
1321321 . Re-run the dry run to ensure all issues have been resolved.
133133
134134 <a href = { successfulDryRun } >
135- <img src = { successfulDryRun } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
135+ <img src = { successfulDryRun } className = " chapter-image " />
136136 </a >
137137
138138<h3 class = " chapter-sub-heading" >Examples of Dry Run Errors</h3 >
@@ -142,25 +142,25 @@ Some examples of dry run errors are:
1421421 . ** Invalid Field Value** : The error message indicates that a field has an invalid value. For instance, in the image below, the fields "spec > ports[ 0] > port" and "spec > ports[ 0] > targetPort" have invalid values of 0. These values must be between 1 and 65535, inclusive.
143143
144144 <a href = { drInvalidField1 } >
145- <img src = { drInvalidField1 } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto 20px" }} />
145+ <img src = { drInvalidField1 } className = " chapter-image " style = { { margin: " 0 auto 20px" }} />
146146 </a >
147147
148148 <a href = { drInvalidField2 } >
149- <img src = { drInvalidField2 } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
149+ <img src = { drInvalidField2 } className = " chapter-image " />
150150 </a >
151151
1521521 . ** Missing Required Field**
153153
154154 <a href = { missingField } >
155- <img src = { missingField } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
155+ <img src = { missingField } className = " chapter-image " />
156156 </a >
157157
1581581 . ** Missing Dependencies** : In this case, the error occurs because a Kubernetes [ Custom Resource Definition] ( https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/ ) (CRD) should have been deployed first before attempting to deploy this component.
159159
160160 To resolve this, ensure that all necessary dependencies, such as CRDs, are deployed before deploying the components that rely on them.
161161
162162 <a href = { missingResource } >
163- <img src = { missingResource } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
163+ <img src = { missingResource } className = " chapter-image " />
164164 </a >
165165
166166<h2 class = " chapter-sub-heading" >Environment Selection</h2 >
@@ -176,25 +176,25 @@ You can add an environment through the deployment modal by following these steps
1761761 . Click on ** Add Environments**
177177
178178 <a href = { addEnv } >
179- <img src = { addEnv } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
179+ <img src = { addEnv } className = " chapter-image " />
180180 </a >
181181
1821821 . Select ** Create** and put in a name for the environment, _ e.g.Development_ , and ** Save** .
183183
184184 <a href = { createEnv } >
185- <img src = { createEnv } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
185+ <img src = { createEnv } className = " chapter-image " />
186186 </a >
187187
1881881 . After creating the environment you add connections to the environment, here we want to add a Kubernetes cluster. Click on the ** arrows** icon to open the Development Resources modal.
189189
190190 <a href = { assignConn } >
191- <img src = { assignConn } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
191+ <img src = { assignConn } className = " chapter-image " />
192192 </a >
193193
194194 ** Available Connections** on the left side shows a list of Kubernetes clusters that are currently managed by Meshery.
195195
196196 <a href = { kubeConn } >
197- <img src = { kubeConn } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
197+ <img src = { kubeConn } className = " chapter-image " />
198198 </a >
199199
200200
@@ -207,7 +207,7 @@ You can add an environment through the deployment modal by following these steps
207207During the deployment, if a connection has not yet been added to your environment, it will appear as shown below.
208208
209209<a href = { missingCon } >
210- <img src = { missingCon } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
210+ <img src = { missingCon } className = " chapter-image " />
211211</a >
212212
213213In this scenario, to add a new environment.
@@ -225,7 +225,7 @@ Another way to add a connection to an Environment is by selecting an environment
2252251 . Identify the desired connection. Under the ** Environment** section, click the dropdown menu to add and select the environment you want to associate with your connection.
226226
227227 <a href = { envConn } >
228- <img src = { envConn } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
228+ <img src = { envConn } className = " chapter-image " />
229229 </a >
230230
231231<h3 class = " chapter-sub-heading" >Verifying Kubernetes Connections</h3 >
@@ -234,15 +234,15 @@ The Kubernetes connection icon at the top right corner of the screen shows the l
234234Clicking on the icon will invoke an ad hoc connectivity test between your Meshery Server and the specific Kubernetes cluster. Should this check fail, verify the health of your Meshery Operator deployment within that cluster.
235235
236236<a href = { connList } >
237- <img src = { connList } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
237+ <img src = { connList } className = " chapter-image " />
238238</a >
239239
240240<h3 class = " chapter-sub-heading" >Environment Error</h3 >
241241
242242If your environment is not properly set up before deployment, you may encounter the error below.
243243
244244<a href = { envError } >
245- <img src = { envError } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
245+ <img src = { envError } className = " chapter-image " />
246246</a >
247247
248248To handle this error follow the suitable steps for adding a connection to your environment as previously discussed.
@@ -278,21 +278,21 @@ You have the option of using the live cluster provided by Meshery Playground or
2782781 . Click ** Finish** .
279279
280280 <a href = { successDeploy } >
281- <img src = { successDeploy } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
281+ <img src = { successDeploy } className = " chapter-image " />
282282 </a >
283283
284284<h3 class = " chapter-sub-heading" >Deployment Errors</h3 >
285285
2862861 . ** Missing Namespace** : This error occurs when you attempt to create a Kubernetes resource without specifying a namespace. Kubernetes requires that all resources have an associated namespace.
287287
288288 <a href = { missingNs } >
289- <img src = { missingNs } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
289+ <img src = { missingNs } className = " chapter-image " />
290290 </a >
291291
2922921 . ** Empty Label Selector** : This error indicates an empty label selector.
293293
294294 <a href = { emptyLs } >
295- <img src = { emptyLs } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
295+ <img src = { emptyLs } className = " chapter-image " />
296296 </a >
297297
298298<h3 class = " chapter-sub-heading" >Troubleshooting Errors</h3 >
@@ -306,7 +306,7 @@ For the comprehensive list of error codes refer to [Error Code Reference](https:
306306If you encounter persistent issues, consider consulting the [ Meshery Community forum] ( https://discuss.layer5.io/c/meshery/5 ) .
307307
308308<a href = { errorCode } >
309- <img src = { errorCode } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
309+ <img src = { errorCode } className = " chapter-image " />
310310</a >
311311
312312<h3 class = " chapter-sub-heading" >Using the Notification Center for Troubleshooting</h3 >
@@ -322,11 +322,11 @@ The Notification Center in Meshery helps manage events during the deployment pro
3223221 . Keeps a log of past notifications, allowing you to track and review previous errors and their resolutions.
323323
324324<a href = { notification } >
325- <img src = { notification } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
325+ <img src = { notification } className = " chapter-image " />
326326</a >
327327
328328<a href = { notificationCenter } >
329- <img src = { notificationCenter } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 10px auto" }} />
329+ <img src = { notificationCenter } className = " chapter-image " style = { { margin: " 10px auto" }} />
330330</a >
331331
332332By actively monitoring the Notification Center, you can promptly address issues as they arise, ensuring a smoother deployment process. Learn more about [ Managing Events with the Notification Center] ( https://docs.meshery.io/guides/events-management ) .
@@ -339,7 +339,7 @@ To undeploy the resources
3393391 . Click on the ** Undeploy** icon.
340340
341341 <a href = { undeploy } >
342- <img src = { undeploy } style = { {maxWidth: " 500px " , width: " 100% " , height: " auto " , display: " block " , margin: " 0 auto " } } />
342+ <img src = { undeploy } className = " chapter-image " />
343343 </a >
344344
345345
0 commit comments