Closed ghost closed 3 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
/close
@kubevirt-bot: Closing this issue.
Label all operators and infrastructrre components with common lables [0] in order to allow an admin to discover the relationship between all entities - and to allow tools to automatically discover the topology.
Labels to use:
app.kubernetes.io/managed-by: vm-import-operator
app.kubernetes.io/version
– value of theOPERATOR_VERSION
environment variableapp.kubernetes.io/component: kubevirt
app.kubernetes.io/part-of: hyperconverged-cluster
app.kubernetes.io/name
– value should be the name of the resource itself. e.g. "virt-controller"[0] https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/