kops icon indicating copy to clipboard operation
kops copied to clipboard
verified publisher icon kubernetes

Remove vendor directory

Open rifelpet opened this issue 3 years ago • 10 comments

rifelpet avatar Jun 15 '22 22:06 rifelpet

Skipping CI for Draft Pull Request. If you want CI signal for your change, please convert it to an actual PR. You can still manually trigger a test run with /test all

k8s-ci-robot avatar Jun 15 '22 22:06 k8s-ci-robot

/test all

rifelpet avatar Jun 15 '22 22:06 rifelpet

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: To complete the pull request process, please ask for approval from rifelpet after the PR has been reviewed.

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

Needs approval from an approver in each of these files:

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

k8s-ci-robot avatar Jun 15 '22 22:06 k8s-ci-robot

/test pull-kops-e2e-kubernetes-aws

hakman avatar Jun 16 '22 08:06 hakman

/test pull-kops-e2e-kubernetes-aws

hakman avatar Jun 16 '22 15:06 hakman

@rifelpet: PR needs rebase.

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.

k8s-ci-robot avatar Jun 20 '22 00:06 k8s-ci-robot

Should we try to get this one in for 1.25?

olemarkus avatar Jul 08 '22 11:07 olemarkus

Should we try to get this one in for 1.25?

Last discussion we had about this with @justinsb, the answer was negative. Kubernetes still has the vendor dir also.

hakman avatar Jul 08 '22 12:07 hakman

Fair enough

olemarkus avatar Jul 08 '22 13:07 olemarkus

@rifelpet: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-kops-e2e-k8s-gce-cilium bff279bcbdf7d80ae51be6881c28b6e771dd7718 link true /test pull-kops-e2e-k8s-gce-cilium
pull-kops-e2e-aws-karpenter bff279bcbdf7d80ae51be6881c28b6e771dd7718 link true /test pull-kops-e2e-aws-karpenter
pull-kops-e2e-k8s-aws-calico bff279bcbdf7d80ae51be6881c28b6e771dd7718 link true /test pull-kops-e2e-k8s-aws-calico
pull-kops-test bff279bcbdf7d80ae51be6881c28b6e771dd7718 link true /test pull-kops-test
pull-kops-build bff279bcbdf7d80ae51be6881c28b6e771dd7718 link true /test pull-kops-build

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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 avatar Aug 31 '22 07:08 k8s-ci-robot

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Nov 29 '22 08:11 k8s-triage-robot

@rifelpet: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-kops-e2e-k8s-gce-cilium bff279bcbdf7d80ae51be6881c28b6e771dd7718 link true /test pull-kops-e2e-k8s-gce-cilium
pull-kops-e2e-aws-karpenter bff279bcbdf7d80ae51be6881c28b6e771dd7718 link true /test pull-kops-e2e-aws-karpenter
pull-kops-e2e-k8s-aws-calico bff279bcbdf7d80ae51be6881c28b6e771dd7718 link true /test pull-kops-e2e-k8s-aws-calico
pull-kops-test bff279bcbdf7d80ae51be6881c28b6e771dd7718 link true /test pull-kops-test
pull-kops-build bff279bcbdf7d80ae51be6881c28b6e771dd7718 link true /test pull-kops-build
pull-kops-e2e-cni-cilium-eni bff279bcbdf7d80ae51be6881c28b6e771dd7718 link true /test pull-kops-e2e-cni-cilium-eni
pull-kops-e2e-cni-cilium-etcd bff279bcbdf7d80ae51be6881c28b6e771dd7718 link true /test pull-kops-e2e-cni-cilium-etcd

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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 avatar Dec 07 '22 19:12 k8s-ci-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar Jan 06 '23 20:01 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Reopen this PR with /reopen
  • Mark this PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

k8s-triage-robot avatar Feb 05 '23 21:02 k8s-triage-robot

@k8s-triage-robot: Closed this PR.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Reopen this PR with /reopen
  • Mark this PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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.

k8s-ci-robot avatar Feb 05 '23 21:02 k8s-ci-robot