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

Bundle: namespaceSelector #37

Merged
merged 13 commits into from
Jul 21, 2022

Conversation

JoshVanL
Copy link
Contributor

@JoshVanL JoshVanL commented Jul 18, 2022

This PR adds a namespaceSelector option to the bundle.spec.target API.

The namespace selector currently only contains a MatchLabels map[string]string field.

If the label selector is empty, it matches on all Namespaces (the current behaviour).

Hopefully this is quite self explanatory slightly_smiling_face

A target ConfigMap will now receive an event with a relevant message when the target ConfigMap is not deleted because it is not owned by the trust operator.

/assign @munnerz
fixes #1
Docs PR

@jetstack-bot jetstack-bot added dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Jul 18, 2022
Copy link
Member

@SgtCoDFish SgtCoDFish left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve
/hold

Looks like a good improvement to me 😁

I'm a little squeamish about syncing to all namespaces as the default. I'd probably prefer to default only to syncing to the trust namespace; IMO since this project is so new it's reasonable for us to make a breaking change like that.

But that's a tangent from this PR which is good as-is 😁

EDIT: I added a hold since this wasn't assigned to me; maybe you want more eyes on it. If not, happy to unhold and proceed!

@jetstack-bot jetstack-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 20, 2022
@jetstack-bot jetstack-bot added the lgtm Indicates that a PR is ready to be merged. label Jul 20, 2022
@jetstack-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoshVanL, SgtCoDFish

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:
  • OWNERS [JoshVanL,SgtCoDFish]

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

@JoshVanL
Copy link
Contributor Author

@SgtCoDFish As discussed on the standup, I think I agree that syncing to all namespaces by default is probably not the way to go, and we should make the namespace selector a required field in future PRs.

/hold cancel

@jetstack-bot jetstack-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 21, 2022
@SgtCoDFish
Copy link
Member

/test pull-cert-manager-trust-verify

@SgtCoDFish
Copy link
Member

/test pull-cert-manager-trust-smoke

@jetstack-bot jetstack-bot merged commit 16d26e2 into cert-manager:main Jul 21, 2022
@SgtCoDFish
Copy link
Member

As discussed on the standup...

Cool cool; I'll create issues now for that and for the root cert bundle thing we mentioned!

@jaygridley
Copy link
Contributor

Hello @SgtCoDFish, a new version (0.1.2) of the Helm chart with support on CRD level was released, but the functionality in the application itself was not released. It there a plan to align this, please?

@SgtCoDFish
Copy link
Member

Hello @SgtCoDFish, a new version (0.1.2) of the Helm chart with support on CRD level was released, but the functionality in the application itself was not released. It there a plan to align this, please?

Hi! maybe @JoshVanL can help, I can't I'm afraid

@JoshVanL
Copy link
Contributor Author

JoshVanL commented Aug 9, 2022

@jaygridley I'll go ahead with a minor release with this feature now 🙂

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. dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. lgtm Indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Limiting what namespaces trust bundles are synced to
5 participants