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

High Level User Stories #5

Closed
christopherhein opened this issue Oct 27, 2020 · 10 comments
Closed

High Level User Stories #5

christopherhein opened this issue Oct 27, 2020 · 10 comments
Labels
kind/design Categorizes issue or PR as related to design. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Milestone

Comments

@christopherhein
Copy link
Member

  1. As a control plane operator, I want my Kubernetes control plane to have multiple replicas to meet my zero down time needs.
  2. As a control plane operator, I want to be able declare how each control plane is configured.
  3. As a control plane operator, I want to be able to rotate the certificates on all components so that my cluster continues to run
  4. As a developer, I want to be able to use control plane level resources without conflicting with another control plane
  5. As a control plane operator, I want to be able to upgrade to a minor version so my cluster remains supported.
  6. As a control plane operator, I want to be able to know my cluster is working properly after it's been created.
@christopherhein
Copy link
Member Author

@christopherhein
Copy link
Member Author

Please add more User Stories for CAPN

@christopherhein
Copy link
Member Author

We need to add a story about multi-tenancy use cases.

@brightzheng100
Copy link

There should have some level of delegation from super admin to tenant / nested cluster admin(s) so these use cases might be valid as well:

  • As a tenant / nested cluster admin, I want to be able to connect to an authn/authz provider so that I can onboard my users;
  • As a tenant / nested cluster admin, I want to be able to act like a real K8s admin to create cluster-wide objects, e.g. CRDs, namespaces, within my tenant / nested cluster and grant permissions to my users/roles;
  • As a tenant / nested cluster admin, I want to be able to upgrade my nested cluster(s) to available, supported K8s versions independently

@christopherhein
Copy link
Member Author

Thanks @brightzheng100

@christopherhein
Copy link
Member Author

/kind design

@k8s-ci-robot k8s-ci-robot added the kind/design Categorizes issue or PR as related to design. label Nov 19, 2020
@fejta-bot
Copy link

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-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 17, 2021
@christopherhein
Copy link
Member Author

/milestone v0.1.0

@k8s-ci-robot k8s-ci-robot added this to the v0.1.0 milestone Feb 23, 2021
@christopherhein
Copy link
Member Author

/close

@k8s-ci-robot
Copy link
Contributor

@christopherhein: Closing this issue.

In response to this:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/design Categorizes issue or PR as related to design. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants