dra-example-driver icon indicating copy to clipboard operation
dra-example-driver copied to clipboard

WIP: Add instructions for running the example driver on GKE

Open mortent opened this issue 9 months ago • 6 comments

We currently only provide instructions for running the example driver on Kind. We should provide instructions for how to run the driver on other Kubernetes distributions, as they will include some different steps. This PR adds instructions for how to get the example driver running on GKE.

For now this just adds a new section with the new content. Ideally we should restructure the README file, so that we can provide separate instructions for getting the driver running on a cluster, and then a shared section for running the examples. I decided not to do that in this PR, as I want to make sure we have agreement on a structure first. Created an issue for this: https://github.com/kubernetes-sigs/dra-example-driver/issues/94

mortent avatar Apr 09 '25 00:04 mortent

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mortent Once this PR has been reviewed and has the lgtm label, please assign elezar for approval. For more information see the Code Review Process.

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 Apr 09 '25 00:04 k8s-ci-robot

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

k8s-ci-robot avatar May 05 '25 19:05 k8s-ci-robot

@mortent: please address the comments and rebase.

pohly avatar May 13 '25 13:05 pohly

/retitle WIP: Add instructions for running the example driver on GKE

pohly avatar Jul 21 '25 07:07 pohly

The Kubernetes project currently lacks enough contributors to adequately respond to all 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:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this 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 Oct 19 '25 07:10 k8s-triage-robot