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

allow webconsole to discover cluster information #18075

Merged

Conversation

deads2k
Copy link
Contributor

@deads2k deads2k commented Jan 11, 2018

Adds permissions to the webconsole to inspect what clusterservicebrokers are present.

@pmorie please confirm this is a non-escalating resource which can be generally viewed.
@openshift/sig-security
@spadgett @jwforres you'll need this before merging openshift/origin-web-console-server#18

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 11, 2018
@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 11, 2018
@bparees bparees removed their request for review January 11, 2018 17:05
@coreydaley coreydaley removed their request for review January 11, 2018 18:09
@deads2k
Copy link
Contributor Author

deads2k commented Jan 11, 2018

@jpeeler are clusterservicebrokers safe for most people to see

@spadgett
Copy link
Member

@sdodson I'm working on corresponding openshift-ansible changes for this

@jpeeler
Copy link

jpeeler commented Jan 11, 2018

@deads2k
Copy link
Contributor Author

deads2k commented Jan 11, 2018

@jpeeler are clusterservicebrokers safe for most people to see

Confirmed via irc with @jpeeler and in person with @pmorie that we are ok to expose this.

@liggitt
Copy link
Contributor

liggitt commented Jan 11, 2018

interesting... the web console server is doing live lookup to build config now?

@deads2k
Copy link
Contributor Author

deads2k commented Jan 11, 2018

interesting... the web console server is doing live lookup to build config now?

Seems more reliable than having a set config for fully discoverable things. And the versions really have to be live look up'ed I didn't set up watches.

@deads2k
Copy link
Contributor Author

deads2k commented Jan 11, 2018

/retest

name: web-console-server-rbac
parameters:
- name: NAMESPACE
# This namespace cannot be changed. Only `openshift-web-console` is supported.
Copy link
Contributor

Choose a reason for hiding this comment

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

Why make it a parameter then?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Why make it a parameter then?

Template processing will clear them unless you explicitly set it using the variable. This just makes all paramaters for all templates the same.

@enj
Copy link
Contributor

enj commented Jan 12, 2018

Works for me:

$ oc whoami
system:serviceaccount:openshift-web-console:webconsole

$ oc get clusterservicebrokers
NAME                      AGE
template-service-broker   2m

@enj
Copy link
Contributor

enj commented Jan 13, 2018

A related question - does running the console in a pod allow us to make it's OAuth client private now like the request token endpoint? IIRC it already supports the code flow?

That would leave oc as the only remaining public OAuth client, which is expected since it cannot protect any embedded secret, and it already uses PKCE.

@liggitt
Copy link
Contributor

liggitt commented Jan 13, 2018

does running the console in a pod allow us to make it's OAuth client private now like the request token endpoint? IIRC it already supports the code flow?

That would require adding server side oauth handling to the web console, which isn't really worth it if the end goal is to hand the access token over to the user.

@spadgett
Copy link
Member

@enj OK with this change? It's required for several other PRs

@deads2k
Copy link
Contributor Author

deads2k commented Jan 15, 2018

@enj OK with this change? It's required for several other PRs

I suspect so. Tagging and @enj can hold if didn't make it through.

@deads2k deads2k added the lgtm Indicates that a PR is ready to be merged. label Jan 15, 2018
@deads2k
Copy link
Contributor Author

deads2k commented Jan 15, 2018

/retest

@enj
Copy link
Contributor

enj commented Jan 15, 2018

@enj OK with this change? It's required for several other PRs

Yup, just forgot to tag.

/lgtm

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, enj

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@spadgett
Copy link
Member

/retest

@spadgett
Copy link
Member

flake #16994

/retest

openshift-merge-robot added a commit to openshift/openshift-ansible that referenced this pull request Jan 16, 2018
Automatic merge from submit-queue.

Add console RBAC template

Required for openshift/origin-web-console-server#18
Origin changes: openshift/origin#18075

/assign @sdodson 
/cc @deads2k
@deads2k
Copy link
Contributor Author

deads2k commented Jan 16, 2018

/retest

1 similar comment
@deads2k
Copy link
Contributor Author

deads2k commented Jan 16, 2018

/retest

@deads2k
Copy link
Contributor Author

deads2k commented Jan 16, 2018

This blocks a chain of coordinated pulls across three repos. bumping priority.

@deads2k
Copy link
Contributor Author

deads2k commented Jan 16, 2018

/retest

5 similar comments
@deads2k
Copy link
Contributor Author

deads2k commented Jan 16, 2018

/retest

@deads2k
Copy link
Contributor Author

deads2k commented Jan 16, 2018

/retest

@deads2k
Copy link
Contributor Author

deads2k commented Jan 16, 2018

/retest

@deads2k
Copy link
Contributor Author

deads2k commented Jan 16, 2018

/retest

@spadgett
Copy link
Member

/retest

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@spadgett
Copy link
Member

/retest

2 similar comments
@spadgett
Copy link
Member

/retest

@spadgett
Copy link
Member

/retest

@openshift-merge-robot
Copy link
Contributor

/test all [submit-queue is verifying that this PR is safe to merge]

@spadgett
Copy link
Member

/retest

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 17, 2018

@deads2k: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/openshift-jenkins/extended_conformance_gce 98b9fa6 link /test extended_conformance_gce

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

@openshift-merge-robot
Copy link
Contributor

Automatic merge from submit-queue (batch tested with PRs 18075, 17725, 16766, 18070, 18113).

@openshift-merge-robot openshift-merge-robot merged commit 91fbe83 into openshift:master Jan 17, 2018
@pweil-
Copy link

pweil- commented Jan 18, 2018

only 19 retests? That was too easy 🎉

@jpeeler
Copy link

jpeeler commented Jan 18, 2018

It is funny to laugh about (sort of), but shouldn't this be considered a pretty big problem? It seems the test_pull_request_origin_extended_conformance_crio in particular is extremely problematic - https://openshift-gce-devel.appspot.com/pr/18075

@pweil-
Copy link

pweil- commented Jan 18, 2018

It is funny to laugh about (sort of), but shouldn't this be considered a pretty big problem?

Yes, it should be being treated as at least a p1 issue (which is a blocker) if it is something that is occurring all the time. The referenced flake is marked as p1, @mrunalp would have to comment on any progress there.

@spadgett
Copy link
Member

If you look through the failures, it's a generally a different flake each time. We should do a better job of linking to a flake issue for each, but it's a bit disheartening doing it 20 times (multiplied by how many PRs you have open). And it's difficult to track down if you're trying to re-kick the tests from your phone in the evening. I also wonder if there's not an infrastructure issue since jobs fail consistently, but usually on different tests.

Fighting a similar problem now for #18114

@deads2k deads2k deleted the webconsole-07-discovery branch January 24, 2018 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. queue/blocks-others sig/security size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants