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

vastly simplify the image registry trust configmap #287

Merged

Conversation

deads2k
Copy link
Contributor

@deads2k deads2k commented Jan 3, 2020

Use the standard apply methods to gain proper eventing, caching, and diff computation.

/assign @stlaz @adambkaplan

@stlaz @sttts @adambkaplan need a bug written for the direct dependency on the image-registry namespace above. It should never have merged that way. Communication between components happens through openshift-config-manged so we can see who is accessing what and avoid trip deployment deps.

@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jan 3, 2020
@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 3, 2020
@stlaz
Copy link
Member

stlaz commented Jan 6, 2020

/lgtm
Good change, the original code was almost unreadable compared to the new version.

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 6, 2020
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

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

@openshift-merge-robot openshift-merge-robot merged commit f8682db into openshift:master Jan 6, 2020
@adambkaplan
Copy link

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. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants