Skip to content

BUILD-284: Relocate shared resources api into openshift/api repository#979

Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
coreydaley:jira_build_284_integrate_shared_resources_operator
Oct 5, 2021
Merged

BUILD-284: Relocate shared resources api into openshift/api repository#979
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
coreydaley:jira_build_284_integrate_shared_resources_operator

Conversation

@coreydaley
Copy link
Copy Markdown

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 28, 2021

@coreydaley: This pull request references Bugzilla bug 1986557, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.9.0) matches configured target release for branch (4.9.0)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @xiuwang

Details

In response to this:

BUG 1986557: Integrate Shared Resources Operator with Cluster Storage Operator

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.

@openshift-ci openshift-ci Bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Jul 28, 2021
@openshift-ci openshift-ci Bot requested a review from xiuwang July 28, 2021 16:25
@coreydaley
Copy link
Copy Markdown
Author

/assign @adambkaplan @bparees
ptal

@bparees
Copy link
Copy Markdown
Contributor

bparees commented Jul 28, 2021

why is this a bug? looks like part of a feature.

@bparees
Copy link
Copy Markdown
Contributor

bparees commented Jul 28, 2021

/unassign
/assign @mfojtik

@mfojtik please pick one of your trusted api reviewers

@openshift-ci openshift-ci Bot assigned mfojtik and unassigned bparees Jul 28, 2021
@bparees
Copy link
Copy Markdown
Contributor

bparees commented Jul 28, 2021

/hold

since this is going in as a no-FF feature, it will need qe/docs/px acks before it can merge.

but that should not hold up getting an api-review approval.

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 28, 2021
@coreydaley coreydaley changed the title BUG 1986557: Integrate Shared Resources Operator with Cluster Storage Operator [WIP] BUG 1986557: Integrate Shared Resources Operator with Cluster Storage Operator Jul 29, 2021
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 29, 2021
@adambkaplan
Copy link
Copy Markdown
Contributor

adambkaplan commented Jul 29, 2021

/hold

Maintaining the hold due to openshift/csi-driver-shared-resource#39. I've put a few renames in flight to give a coherent branding experience:

  1. API group - sharedresource.openshift.io. New custom resource is share.sharedresource.openshift.io.
  2. CSI Driver name (to be registered by the cluster storage operator) - csi.sharedresource.openshift.io
  3. Repos will be renamed to reflect the unified branding.

The API group and directory structure should be updated here (no longer use projectedresource).

@adambkaplan
Copy link
Copy Markdown
Contributor

/cc @jitendar-singh @rolfedh @RickJWagner

For qe, docs, and PX acks on this.

Comment thread sharedresource/v1alpha1/0000_10_sharedresource.crd.yaml Outdated
Comment thread sharedresource/v1alpha1/0000_10_sharedresource.crd.yaml Outdated
@coreydaley
Copy link
Copy Markdown
Author

@adambkaplan I have updated this pull request to correlate with the renaming of the projected resource driver. Can you ptal and see if this falls in line with your updates?

@coreydaley coreydaley changed the title [WIP] BUG 1986557: Integrate Shared Resources Operator with Cluster Storage Operator BUG 1986557: Integrate Shared Resources Operator with Cluster Storage Operator Jul 30, 2021
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 30, 2021
Copy link
Copy Markdown
Contributor

@adambkaplan adambkaplan left a comment

Choose a reason for hiding this comment

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

I don't think we need the display name. Only other item is to add explicit owners, then it looks good to me.

Comment thread sharedresource/OWNERS
Comment thread sharedresource/v1alpha1/0000_10_sharedresource.crd.yaml Outdated
Comment thread sharedresource/v1alpha1/0000_10_sharedresource.crd.yaml Outdated
Copy link
Copy Markdown
Contributor

@adambkaplan adambkaplan left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 2, 2021
Comment thread storage/v1alpha1/register.go Outdated
Comment thread storage/v1alpha1/types_share.go Outdated
Comment thread storage/v1alpha1/types_share.go Outdated
Comment thread storage/v1alpha1/types_share.go Outdated
@coreydaley
Copy link
Copy Markdown
Author

@deads2k @gabemontero @adambkaplan @jsafrane @soltysh @mfojtik
ptal, pull request has been updated with the new api from https://github.com/openshift/csi-driver-shared-resource/
Note: I am unable to remove the protobuf tags, they get automagically re-added when I run make update. Is that expected behavior?

@gabemontero
Copy link
Copy Markdown
Contributor

/hold cancel

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 1, 2021
Copy link
Copy Markdown
Contributor

@gabemontero gabemontero left a comment

Choose a reason for hiding this comment

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

LGTM but I'll defer to others to apply the appropriate labels

Copy link
Copy Markdown
Contributor

@adambkaplan adambkaplan left a comment

Choose a reason for hiding this comment

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

Looks like there is the one CRD yaml file that was missed, otherwise I think we're in good shape!

Comment thread sharedresource/v1alpha1/0000_10_sharedresource.crd.yaml Outdated
Comment thread sharedresource/OWNERS Outdated
Comment thread sharedresource/v1alpha1/types_share.go Outdated
// `oc create role shared-resource-my-share --verb=use --resource=sharedconfigmaps.sharedresource.openshift.io --resource-name=my-share`
// `oc create rolebinding shared-resource-my-share --role=shared-resource-my-share --serviceaccount=my-namespace:default`
//
// Administrators can create separate Roles and RoleBindings for their users to be able the list and/or view the
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

What do you see the default as? Autthenticated list/watch of SharedConfigMaps and SharedSecrets?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Are you asking if any authenticated user of the cluster will be able to list/watch the shared resources? If not, could you please elaborate on your question?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Are you asking if any authenticated user of the cluster will be able to list/watch the shared resources?

yes. What is the default policy?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'll step in for this one (after discussing this with @coreydaley on slack today, as well has prior discussion I've had with @adambkaplan )

So yeah @coreydaley can augment the godoc here @deads2k, providing a compact summary of the following:

  • we envisioned some aggregation to the default roles .... for this one, I believe we are talking the view role
  • with that, users can get (that is missing in this current version), list, and watch SharedConfigMap and SharedSecret
  • so they can know which actual ConfigMap or Secret is being shared via a get on the SharedConfigMap or SharedSecret
  • but they cannot of course see inside the ConfigMap or Secret unless they have sufficient permissions to those objects in the namespaces they reside
  • minor sidebar - oc describe ... does a get under the covers

Any issues or things we missed there @deads2k ?

thanks

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

In putting ^^ together @deads2k I am working off of https://kubernetes.io/docs/reference/access-authn-authz/rbac/#aggregated-clusterroles and hence believe we could aggregate get/list/watch perms for our 2 new cluster scoped CRDs here, assuming we all agree that is "safe", and I am in fact interpreting that doc correctly.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

@deads2k Updated with default permissions information. ptal

Comment thread sharedresource/v1alpha1/types_share.go Outdated
@deads2k
Copy link
Copy Markdown
Contributor

deads2k commented Oct 4, 2021

after the reference and default policy, I think it is ready to merge.

@deads2k
Copy link
Copy Markdown
Contributor

deads2k commented Oct 5, 2021

/lgtm
/approve

@deads2k
Copy link
Copy Markdown
Contributor

deads2k commented Oct 5, 2021

/lgtm cancel

@openshift-ci openshift-ci Bot added lgtm Indicates that a PR is ready to be merged. and removed lgtm Indicates that a PR is ready to be merged. labels Oct 5, 2021
Comment thread sharedresource/v1alpha1/types_shared_secret.go
Operator

Co-authored-by: Adam Kaplan <adam.kaplan@redhat.com>
Co-authored-by: Gabe Montero <gmontero@redhat.com>
@coreydaley
Copy link
Copy Markdown
Author

@deads2k Updated per your request, ptal.

@deads2k
Copy link
Copy Markdown
Contributor

deads2k commented Oct 5, 2021

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Oct 5, 2021
@openshift-merge-robot openshift-merge-robot merged commit 4ec2bbe into openshift:master Oct 5, 2021
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Oct 5, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: coreydaley, deads2k, gabemontero, rolfedh, soltysh

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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. docs-approved Signifies that Docs has signed off on this PR lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.