Kind: Add user stories

Created on 5 Dec 2018 · 9Comments · Source: kubernetes-sigs/kind

Before we dive too deep into execution lets outline some of the concrete user stories.

/cc @kubernetes/sig-cluster-lifecycle

lifecyclrotten

Source

timothysc

👍1

Most helpful comment

I have implemented for helm charts testing if that is what you are looking for:
https://github.com/rimusz/charts/tree/master/test
https://github.com/jfrog/charts/tree/master/test
https://github.com/keel-hq/keel/tree/master/.test

all these are part go the testing pipeline run in circles/travisci

Also an example in https://github.com/helm/chart-testing/tree/master/examples/kind

rimusz on 5 Dec 2018

❤1 👍1

All 9 comments

all these are part go the testing pipeline run in circles/travisci

Also an example in https://github.com/helm/chart-testing/tree/master/examples/kind

rimusz on 5 Dec 2018

❤1 👍1

Right now we're planning to outline the following user stories.

kubeadm user stories
- local developer
- advanced developer (HA)
- CI signal
cluster-api stories
- bootstrap integration
K8s integrator
- CI automation tooling
  
  ...

timothysc on 5 Dec 2018

👍1

@munnerz @Katharine if you get some time, mind helping provide a few details for your existing usage?

BenTheElder on 5 Dec 2018

@BenTheElder Where should we PR user stories?

timothysc on 6 Dec 2018

Maybe docs/design/* -> docs/design/user-stories/* ? Open to suggestions, but probably somewhere within docs/*

BenTheElder on 6 Dec 2018

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 28 Apr 2019

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 28 May 2019

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 27 Jun 2019

@fejta-bot: Closing this issue.

In response to this:

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.