CEL support

[EmilienM]

/kind feature

Describe the solution you'd like

• Add testing structure (ginkgo based) for API testing with CEL
• Add CEL to our APIs

I think this issue can be closed once we have the testing structure and at least one CEL + its test, successfully working.

[jichenjc]

Add testing structure (ginkgo based) for API testing with CEL

seems this are for general API handling, are we introducing CEL for openstackcluster/openstackmachine etc API handling?
just curious on the use case which have description here will be helpful

[EmilienM]

Good question, I thought it would be for general API in types. But I might be wrong and we'll add that for openstack*. cc @mdbooth ?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[EmilienM]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[mdbooth]

@EmilienM Should we close this? Seems like we've pretty much gone this way now.

[EmilienM]

indeed
/close

[k8s-ci-robot]

@EmilienM: Closing this issue.

In response to this:

indeed
/close

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.