Improve gather metrics pipeline - Githubissues

AICoE / aicoe-ci

AICoE-CI using TektonCD pipelines and triggers

13 stars 13 forks source link

Improve gather metrics pipeline #118

Closed pacospace closed 2 years ago

pacospace commented 3 years ago

Is your feature request related to a problem? Please describe. Improve gather metrics pipeline

Describe the solution you'd like

[x] Add env variable for namespace deployment, leave aicoe-ci as default
[ ] Add namespace deployment to .aicoe.yaml check
[x] Add task for platform metrics gathering
[ ] doc for users to create roles (DOC)
[ ] SA for custom deployment for users
[x] add secrets for Ceph
[x] add runtime for test (default to root) to .aicoe.yaml
[x] add test name for test type (e.g. feature name for behave) to .aicoe.yaml
[x] allow multiple deployments from the same repo.
[ ] Include docs link in the PR comment explaining the goal of the pipeline.

Describe alternatives you've considered Leave as it is.

Additional context

harshad16 commented 2 years ago

@Gregory-Pereira would like to assist with remaining.

The remaining task is to enable users to give their namespace information through the .aicoe-ci.yaml and the aicoe-ci would deploy the deployment in that namespace. To deploy an app in a different namespace, via an app in another namespace, the service account(SA) requires access to the namespace (which is gained via roles).

sesheta commented 2 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

harshad16 commented 2 years ago

/remove-lifecycle stale

sesheta commented 2 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

sesheta commented 2 years ago

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

sesheta commented 2 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

sesheta commented 2 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/AICoE/aicoe-ci/issues/118#issuecomment-1186731667): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.