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
Update deployment annotation handling to match devfile/api
Adapt handling of additional annotations on the workspace Deployment to
match what is expected from the devfile API (Annotations field on
container components).
As part of supporting this, removes support for specifying additional
annotations/labels via attributes.
Signed-off-by: Angel Misevski <amisevsk@redhat.com>
Copy file name to clipboardExpand all lines: docs/additional-configuration.md
-18Lines changed: 0 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -122,24 +122,6 @@ data:
122
122
123
123
Note: As for automatically mounting secrets, it is necessary to apply the `controller.devfile.io/watch-secret` label to git credentials secrets
124
124
125
-
## Applying labels and annotations to the workspace deployment
126
-
In some cases, it is useful to apply additional labels or annotations to the deployment that is created for a DevWorkspace. This is supported by setting attributes `controller.devfile.io/deployment-labels` and `controller.devfile.io/deployment-annotations` in the DevWorkspace's attributes field. The value of these attributes should be specified as a string map, as it is for regular metadata labels and annotations. For example:
127
-
```
128
-
kind: DevWorkspace
129
-
apiVersion: workspace.devfile.io/v1alpha2
130
-
metadata:
131
-
name: my-workspace
132
-
spec:
133
-
template:
134
-
attributes:
135
-
controller.devfile.io/deployment-labels:
136
-
my-label: foo
137
-
my-other-label: bar
138
-
controller.devfile.io/deployment-annotations:
139
-
my-attribute: foo
140
-
my-other-attribute: bar
141
-
```
142
-
143
125
## Debugging a failing workspace
144
126
Normally, when a workspace fails to start, the deployment will be scaled down and the workspace will be stopped in a `Failed` state. This can make it difficult to debug misconfiguration errors, so the annotation `controller.devfile.io/debug-start: "true"` can be applied to DevWorkspaces to leave resources for failed workspaces on the cluster. This allows viewing logs from workspace containers.
0 commit comments