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: Support optional Name, Namespace for cel readiness rules #2536

Merged

Conversation

barney-s
Copy link
Collaborator

Change description

Support Name,Namespace when setting up readiness rules:

  • In addition to GVK, we want to support Name, Namespace to have custom rule per object.
  • Name and Namespace are optional.

@barney-s
Copy link
Collaborator Author

/assign @justinsb
/assign @hankfreund

- In addition to GVK, we want to support Name, Namespace to have custom rule per object.
- Name and Namespace are optional.
@hankfreund
Copy link
Member

/approve

@hankfreund
Copy link
Member

/lgtm

@google-oss-prow google-oss-prow bot added the lgtm label Aug 20, 2024
@barney-s
Copy link
Collaborator Author

/approve

Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: barney-s, hankfreund

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

@google-oss-prow google-oss-prow bot merged commit 03165e3 into GoogleCloudPlatform:master Aug 20, 2024
11 checks passed
@barney-s barney-s deleted the cel-readiness-2 branch August 21, 2024 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants