High Level User Stories

kubernetes-retired / cluster-api-provider-nested

Cluster API Provider for Nested Clusters

Apache License 2.0

301 stars 67 forks source link

High Level User Stories #5

Closed christopherhein closed 3 years ago

christopherhein commented 4 years ago

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

christopherhein commented 4 years ago

@salaxander @Fei-Guo @weiling61 @charleszheng44

christopherhein commented 4 years ago

Please add more User Stories for CAPN

christopherhein commented 4 years ago

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

brightzheng100 commented 3 years ago

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 commented 3 years ago

Thanks @brightzheng100

christopherhein commented 3 years ago

/kind design

fejta-bot commented 3 years ago

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

christopherhein commented 3 years ago

/milestone v0.1.0

christopherhein commented 3 years ago

/close

k8s-ci-robot commented 3 years ago

@christopherhein: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/cluster-api-provider-nested/issues/5#issuecomment-805079254): >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.