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

Umbrella: UX and "getting started" experience improvements #276

Closed
detiber opened this issue Oct 17, 2018 · 10 comments
Closed

Umbrella: UX and "getting started" experience improvements #276

detiber opened this issue Oct 17, 2018 · 10 comments
Assignees
Labels
kind/documentation Categorizes issue or PR as related to documentation. kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@detiber
Copy link
Member

detiber commented Oct 17, 2018

/kind feature
/priority important-soon

The current getting started experience and general user UX is pretty hostile.

  • Help reduce user confusion between bootstrapping the cluster-api components, cluster creation, and pivoting.
  • Ensure prerequisites are clear and fully defined
  • Documentation around how to configure cluster/machines
  • Explain how to scale a cluster
  • etc...

/assign @detiber @randomvariable

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Oct 17, 2018
@detiber detiber added this to the 20181108 milestone Oct 22, 2018
@detiber detiber modified the milestones: 20181108, 20181122 Nov 8, 2018
@chuckha chuckha modified the milestones: 20181122, 20181206 Nov 15, 2018
@detiber detiber changed the title UX and "getting started" experience improvements Umbrella: UX and "getting started" experience improvements Nov 28, 2018
@timothysc timothysc added the kind/documentation Categorizes issue or PR as related to documentation. label Jan 4, 2019
@rdodev
Copy link
Contributor

rdodev commented Jan 15, 2019

  • CLIs:
    • There are several places where things can go sideways and the user has no idea where to start looking for errors.
    • CLIs should try to provide feedback more actively
    • When not possible to provide real-time feedback, the CLIs should at the very least instruct the user for next steps/debugging (like kubeadm reset for instance)
    • CLIs should be more verbose by default
  • Documentation:
    • Troubleshooting guide
    • Implicit requirements:
      • registry with push permissions
      • image must be public (or else how to pass credentials inside DIND)
  • Pre-flight checks:
    • For every action that has potentially bad non-recoverable states we should try to verify that all critical parts work.

@ncdc
Copy link
Contributor

ncdc commented Mar 25, 2019

/milestone Next

@k8s-ci-robot k8s-ci-robot modified the milestones: v1alpha1, Next Mar 25, 2019
@ncdc
Copy link
Contributor

ncdc commented Mar 25, 2019

I'd like to close this and replace it with as many individual issues as needed to cover the various UX and getting started issues. If we need a way to combine them, we could consider using a milestone or a GitHub project perhaps? What do y'all think?

@detiber
Copy link
Member Author

detiber commented Mar 25, 2019

+1 for github projects, I'd like to avoid overloading the use of milestones.

@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-testing, kubernetes/test-infra and/or fejta.
/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 Jun 23, 2019
@vincepri
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 24, 2019
@chuckha
Copy link
Contributor

chuckha commented Jul 1, 2019

Please break this down into smaller issues and close this issue when done

@randomvariable
Copy link
Member

I think we should close this now that we have the quick start guide?

@vincepri
Copy link
Member

/close

@k8s-ci-robot
Copy link
Contributor

@vincepri: 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.

enxebre pushed a commit to enxebre/cluster-api-provider-aws-2 that referenced this issue Jan 24, 2020
Drop openshift/cluster-api in favour of machine-api-operator
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

9 participants