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

Feature scope #1949

Closed
wants to merge 3 commits into from
Closed

Feature scope #1949

wants to merge 3 commits into from

Conversation

vlal-zz
Copy link

@vlal-zz vlal-zz commented May 15, 2017

  • Add scope to k8s dashboard

As per #1577

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label May 15, 2017
@vlal-zz vlal-zz closed this May 15, 2017
@vlal-zz vlal-zz reopened this May 15, 2017
Address string `json:"address"`
}

// GetScope returns a populated Scope struct.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy-pasted comment?

* @export
*/
pingScope(tries) {
if (tries < 5) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Calling pingScope(5) will do nothing, right? I initially was a little confused by this.
Can you refactor this argument (e.g. to decrease until 0), or add a comment about its meaning?

@codecov
Copy link

codecov bot commented May 18, 2017

Codecov Report

Merging #1949 into master will decrease coverage by 0.37%.
The diff coverage is 29.74%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1949      +/-   ##
==========================================
- Coverage   59.08%   58.71%   -0.38%     
==========================================
  Files         582      587       +5     
  Lines       12171    12328     +157     
==========================================
+ Hits         7191     7238      +47     
- Misses       4811     4919     +108     
- Partials      169      171       +2
Impacted Files Coverage Δ
src/app/frontend/scope/state.js 100% <100%> (ø)
src/app/frontend/chrome/nav/nav_component.js 93.33% <100%> (+0.22%) ⬆️
src/app/frontend/index_module.js 100% <100%> (ø) ⬆️
src/app/frontend/scope/controller.js 2.12% <2.12%> (ø)
src/app/backend/handler/apihandler.go 26.28% <21.95%> (-0.09%) ⬇️
src/app/backend/resource/scope/scope.go 41.5% <41.5%> (ø)
src/app/frontend/scope/module.js 75% <75%> (ø)
src/app/frontend/scope/stateconfig.js 88.88% <88.88%> (ø)
... and 3 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 53876ed...bcb5ea5. Read the comment docs.

func PostScope(client client.Interface) (*Scope, error) {
log.Print("Installing scope on the cluster")

response, err := http.Get("https://cloud.weave.works/launch/k8s/weavescope.yaml?k8s-service-type=NodePort")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the part I'm worried about. It allows cloud.weave.works to hack user's cluster. Can we embed the YAML in repository here and versionize it? It'd be a bit safer at least.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bryk I believe that's been resolved now. Could you please review the rest of this PR and let @vlal and myself know if you broadly approve of it before we rebase and update? Thanks!

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

Prevent issues from auto-closing with an /lifecycle frozen comment.

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 Jan 4, 2018
@errordeveloper
Copy link
Member

Let's get back to this!

/remove-lifecycle stale

cc @danielromlein @bryk

@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 Jan 20, 2018
@maciaszczykm
Copy link
Member

maciaszczykm commented Jan 20, 2018

@errordeveloper I think it is not the best time. We are migrating the whole app to new Angular and it would be better to wait for it. Let's wait for #2727 and return to this discussion then.

@errordeveloper
Copy link
Member

errordeveloper commented Jan 20, 2018 via email

@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 Apr 20, 2018
@fejta-bot
Copy link

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
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 20, 2018
@fejta-bot
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants