remove sigs and introduce dev-kkp team

[buraksekili]

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

What type of PR is this?

Special notes for your reviewer:

Does this PR introduce a user-facing change? Then add your Release Note here:

NONE

Documentation:

NONE

[kron4eg]

/approve

[kubermatic-bot]

LGTM label has been added.

Details

Git tree hash: f67090e17e66a3c600335ee5379cbf599f3d9c0d

[kubermatic-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kron4eg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [kron4eg]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[buraksekili]

/cherrypick release/v1.10

[buraksekili]

/cherrypick release/v1.9

[buraksekili]

/cherrypick release/v1.8

[kubermatic-bot]

@buraksekili: new pull request created: #618

Details

In response to this:

/cherrypick release/v1.10

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-sigs/prow repository.

[kubermatic-bot]

@buraksekili: #617 failed to apply on top of branch "release/v1.8":

Applying: remove sigs and introduce dev-kkp team
Using index info to reconstruct a base tree...
M	OWNERS_ALIASES
Falling back to patching base and 3-way merge...
Auto-merging OWNERS_ALIASES
CONFLICT (content): Merge conflict in OWNERS_ALIASES
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 remove sigs and introduce dev-kkp team

Details

In response to this:

/cherrypick release/v1.8

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-sigs/prow repository.

[kubermatic-bot]

@buraksekili: new pull request created: #619

Details

In response to this:

/cherrypick release/v1.9

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-sigs/prow repository.