You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Integrate GitOps with Secrets Management.md
+4-16Lines changed: 4 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -319,25 +319,13 @@ In this documentation we will add volume mounting to a deployment and configure
319
319
apiVersion: apps/v1
320
320
kind: Deployment
321
321
metadata:
322
-
creationTimestamp: null
323
-
labels:
324
-
app.kubernetes.io/name: taxi
325
-
app.kubernetes.io/part-of: app-taxi
326
-
name: taxi
327
-
namespace: dev
322
+
name: taxi
323
+
namespace: dev
328
324
spec:
329
325
replicas: 1
330
-
selector:
331
-
matchLabels:
332
-
app.kubernetes.io/name: taxi
333
-
app.kubernetes.io/part-of: app-taxi
334
-
strategy: {}
335
326
template:
336
327
metadata:
337
-
creationTimestamp: null
338
-
labels:
339
-
app.kubernetes.io/name: taxi
340
-
app.kubernetes.io/part-of: app-taxi
328
+
...
341
329
spec:
342
330
containers:
343
331
- image: nginxinc/nginx-unprivileged:latest
@@ -358,7 +346,7 @@ spec:
358
346
readOnly: true
359
347
volumeAttributes:
360
348
secretProviderClass: "my-aws-provider"
361
-
status: {}
349
+
...
362
350
```
363
351
Click `REFRESH` on the target application page to apply the updated deployment manifest. Then you can observe that all resources will be successfully synced up.
0 commit comments