[doc] Improve verification steps for defining workspace deployment labels&annotations article
See original GitHub issueand
apiVersion: 1.0.0
metadata:
name: quarkus-quickstarts-l263x
...
Expected: labels / annotations as presented in the examples: https://www.eclipse.org/che/docs/che-7/end-user-guide/creating-a-workspace-from-remote-devfile/#allowing-users-to-define-workspace-deployment-labels-and-annotations_che
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Kubernetes Annotations and Labels - Harness.io Docs
Harness applies labels during Kubernetes deployment that you can use to select objects you defined in your Harness Service Manifests ...
Read more >Understand the deployment process - Power BI - Microsoft Learn
Understand how deployment pipelines, the Power BI Application lifecycle management (ALM) tool, works.
Read more >Delivery pipeline and target configuration - Google Cloud
Target configuration supports annotations and labels, but Google Cloud Deploy does not require them. Annotations and labels are stored with the target resource....
Read more >Chapter 3. Developer workspaces - Red Hat Customer Portal
Allowing users to define workspace deployment labels and annotations. This section describes how to customize workspace deployment labels and annotation using ...
Read more >Well-Known Labels, Annotations and Taints - Kubernetes
Kubernetes reserves all labels and annotations in the kubernetes.io and k8s.io namespaces. This document serves both as a reference to the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Wait … That’s where the confusion is: I should have looked at the deployment label and not at the devfile.
We should probably be more specific in the documentation: add verification steps:
“In the OpenShift console @@ do this to display the deployment labels @@”
Issues go stale after
180
days of inactivity.lifecycle/stale
issues rot after an additional7
days of inactivity and eventually close.Mark the issue as fresh with
/remove-lifecycle stale
in a new comment.If this issue is safe to close now please do so.
Moderators: Add
lifecycle/frozen
label to avoid stale mode.