Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guide for monitoring tests run by CI on Kubernetes - final push #5448

Closed
wants to merge 179 commits into from

Conversation

RobertKielty
Copy link
Member

@RobertKielty RobertKielty commented Jan 30, 2021

Re-submission of the Test Monitoring Guide written by @alejandrox1

We will apply feedback as requested by @justaugustus here on the original PR

Origin thread on Slack

@spiffxp @thejoycekung @hasheddan @jeremyrickard @justaugustus

alejandrox1 and others added 30 commits December 7, 2020 11:49
This should help provide context on how CI works and what processes to
follow to maintain our tests.

Signed-off-by: alejandrox1 <[email protected]>
Signed-off-by: Ricardo Pchevuzinske Katz <[email protected]>
Signed-off-by: Edrick Wong <[email protected]>

Project URL: https://github.com/deislabs/akri

Description of Request:
Need a place to discuss Akri matters with the community
This should make it more APAC/EU friendly too.
**Which issue(s) this PR fixes**:
N/A

First of all! Hi!

We're a project called `odo` located here:

https://github.com/openshift/odo

**Information about us:**

We're an open source project that focuses on specifically on Kubernetes.
We also add support for other Kubernetes-based platforms, but our main
focus in k8s.

In a nutshell, odo is a tool that abstracts specific Kubernetes concepts
for an easier deployment of applications.

Our site is located here: https://odo.dev/ if you'd like to try it out!

**Purpose of the channel:**

For the past.. about a year. We've been using our own public slack channel
located here: http://openshiftdo.slack.com/

We have 100+ members and we're constantly chatting. Our motivation to
join kubernetes.slack.com is because well.. most of us are already on
the Kubernetes slack! That and the fact that we're a dedicated and
Kubernetes-focused project.

**Criteria:**

I believe we fit all the criteria, we're:

- An open source project
- Kubernetes-specific
- Not product focused / proprietary

**Chatroom name requested:**

`odo`

**About the team:**

Charlie Drage (cdrage on GitHub):

- Maintainer / core contributor of: http://github.com/kubernetes/kompose
which already has a Kubernetes #kompose channel

Tomas Kral (kadel on GitHub):

- Past maintainer / contributor of: http://github.com/kubernetes/kompose

Girish Ramnani (girishramnani on GitHub):

- Golang meetup organizer and open source contributor to HashiCorp,
OpenShift and Terraform projects.

Dharmit Shah (dharmit on GitHub):

- Open source contributor to OpenShift, CentOS, MiniShift and Che
projects.

Many thanks and let us know if you need anything else!

We will most likely do another PR requesting updates to usergroups.yaml
so we can ping (for example: odo-devs) or something similar to that.

Signed-off-by: Charlie Drage <[email protected]>
As per September 22, 2020 meeting of SIG Release, we've decided
that the working group's discussions have led to positive changes
and have run their course.  Remaining discussion and operational
points have reasonable ownership, for example in SIG Release and WG
Reliability.

Signed-off-by: Tim Pepper <[email protected]>
**Which issue(s) this PR fixes**:

N/A

**Channel:**

`#odo`

**Request:**

We'd like to be able to have the ability for users to ping `odo-devs` in
the channel in order to contact maintainers.

I have gone through each user's GitHub / Slack ID and added it to
`users.yaml` and created a new users group.

Many thanks!

Signed-off-by: Charlie Drage <[email protected]>
This updates flaky-tests.md with all of the information on finding and deflaking tests from the presentation to SIG Testing found here: https://www.youtube.com/watch?v=Ewp8LNY_qTg
Also, this drops the outdated "Hunting flaky unit tests" section from flaky-tests.md.

Co-authored-by: Aaron Crickenberger <[email protected]>
This commit adds a role description for technical leads in the
Kubernetes community.

Signed-off-by: Sascha Grunert <[email protected]>
This links both documents together to enhance their visibility.

Signed-off-by: Sascha Grunert <[email protected]>
The weekly meetings are moved to monthly. Let's keep reference generic in case
the meeting time change in future.
This adds HAProxy Ingress, [link](https://haproxy-ingress.github.io/), as a new channel at Kubernetes' Slack workspace. HAProxy Ingress is a community driven ingress controller for HAProxy loadbalancer.
The channel was dedicated to the development of the ELK helm chart. The
original maintainers have discussion back to the main charts channel.
@k8s-ci-robot k8s-ci-robot added sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/docs Categorizes an issue or PR as relevant to SIG Docs. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/security Categorizes an issue or PR as relevant to SIG Security. sig/service-catalog Categorizes an issue or PR as relevant to SIG Service Catalog. sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/testing Categorizes an issue or PR as relevant to SIG Testing. sig/ui Categorizes an issue or PR as relevant to SIG UI. sig/usability Categorizes an issue or PR as relevant to SIG Usability. sig/windows Categorizes an issue or PR as relevant to SIG Windows. ug/big-data Categorizes an issue or PR as relevant to ug-big-data. wg/api-expression Categorizes an issue or PR as relevant to WG API Expression. wg/iot-edge Categorizes an issue or PR as relevant to WG IOT Edge. wg/multitenancy Categorizes an issue or PR as relevant to WG Multitenancy. wg/naming Categorizes an issue or PR as relevant to WG Naming. wg/policy Categorizes an issue or PR as relevant to WG Policy. labels Jan 30, 2021
@k8s-ci-robot
Copy link
Contributor

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
  • If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
  • Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

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. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Jan 30, 2021
@jk
Copy link

jk commented Jan 30, 2021

@RobertKielty be more cautious when you mention someone, I've nothing todo with this project.

@RobertKielty RobertKielty deleted the triage-tests-2 branch January 30, 2021 12:21
@justaugustus
Copy link
Member

@RobertKielty be more cautious when you mention someone, I've nothing todo with this project.

@jk -- Mistakes happen. Being kind when they do also matters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/community-management area/contributor-comms Issues or PRs related to the upstream marketing team area/contributor-guide Issues or PRs related to the contributor guide area/contributor-summit Issues or PRs related to all Contributor Summit events area/developer-guide Issues or PRs related to the developer guide area/github-management Issues or PRs related to GitHub Management subproject area/mentorship-planning Relating to strategy, planning,& executing of mentoring programs. NOT specific mentoring opportunty. area/na-summit Issues or PRs related to the Contributor Summit in North America area/slack-management Issues or PRs related to the Slack Management subproject cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. committee/steering Denotes an issue or PR intended to be handled by the steering committee. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/docs Categorizes an issue or PR as relevant to SIG Docs. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/security Categorizes an issue or PR as relevant to SIG Security. sig/service-catalog Categorizes an issue or PR as relevant to SIG Service Catalog. sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/testing Categorizes an issue or PR as relevant to SIG Testing. sig/ui Categorizes an issue or PR as relevant to SIG UI. sig/usability Categorizes an issue or PR as relevant to SIG Usability. sig/windows Categorizes an issue or PR as relevant to SIG Windows. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. ug/big-data Categorizes an issue or PR as relevant to ug-big-data. wg/api-expression Categorizes an issue or PR as relevant to WG API Expression. wg/iot-edge Categorizes an issue or PR as relevant to WG IOT Edge. wg/multitenancy Categorizes an issue or PR as relevant to WG Multitenancy. wg/naming Categorizes an issue or PR as relevant to WG Naming. wg/policy Categorizes an issue or PR as relevant to WG Policy.
Projects
None yet
Development

Successfully merging this pull request may close these issues.