Thanks to visit codestin.com
Credit goes to github.com

Skip to content

UI support changes #7122

@lavalamp

Description

@lavalamp

These items block further progress on the UI. I'm merging #7056 so we can make progress, but it is in general not yet safe to accept UI changes because we are missing various supporting functionality: we don't have enough automated checks in place. Please copy me (@lavalamp) on all UI changes.

P0 items: (I'm unlikely to accept UI changes that aren't working towards fixing one of these issues)

  • Travis/shippable to run the karma tests.
  • Travis/shippable to run the protractor tests.
  • Test to verify that go bin data matches the files output by npm install; npm start (i.e., hack/build-ui.sh has been run)
  • Test to verify that npm install; npm start has been correctly run (the packaged js/css/html files have been assembled from source)
  • www/README.md needs major changes:
    • Make it clear how to build files for inclusion in apiserver binary.
    • Make it clear how to run in standalone mode.
    • Make it clear that these are two distinct modes.
    • Either remove all mention of kubectl, or make it clear that there's a third operational mode, where kubectl proxies your cluster's master, and you run the UI locally pointed at that proxy.
    • work item: make development.json auto-generated from your .kube/config file; actually provide a separate command for generating the files for inclusion in apiserver that doesn't use development.json.
    • Provide more detailed installation instructions.

P1 items:

  • UI to be served from a pod, not from apiserver.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/uipriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions