kubernetes
Common Application Description
The app def working group two things have come out to describe applications.
- A recommended set of labels and annotations (currently in a PR). Note that a) this was worked through both the App Def WG and SIG Apps (which owns the output) and b) everything is prefixed as labels and annotations not prefixed are considered private.
- An application CRD to provide a top level application object. The work for this just started under SIG Apps as owners of the code.
Given this, on the charts repo we got PRs to add metadata descriptions due to this.
Instead of a top level description can we move this to either a prefixed description or wait on the Application CRD?
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.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /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.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten /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.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
The recommendation around labels starts to be adopted and having the UI/UX leverage this labels is the main goal of it. So instead of displaying in the UI only the labels list
- labels: l1=v1, l2=v2, app.kubernertes.io/name=mysql, app.kubernertes.io/version=3.4.5, app.kubernertes.io/instance=production, app.kubernertes.io/part-of: wordpress
we could extract the information and apply a different layout if the label exists:
Mysql - production
Version 3.4.5
part-of wordpress
labels: l1=v1, l2=v2
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.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@maciaszczykm: Reopened this issue.
In response to this:
/reopen /lifecycle frozen /remove-lifecycle rotten
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Is the “Application” CRD something that this Dashboard repo / project should own?
