GEP: Direct Policy Attachment

[youngnick]

Split out of #713.

This GEP covers work to define and implement an example Direct Policy (most likely BackendTLSPolicy, GEP #1897, since that's already existent and is a Direct Policy.)

This includes at a minimum:

• defining what makes a Direct Policy
• suggested patterns for ensuring discoverable status

Graduation criteria will be something like:

• At least one included Direct Policy
• Included Policy must have conformance tests
• Included Policy may be Extended support (and so, optional).

[youngnick]

/kind gep

[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

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[guicassolato]

/remove-lifecycle rotten

[wpbeckwith]

I know this was split off from #713 but I'm confused as to where circuit breakers from the issue landed. Is that here or in the inherited policy attachment issue?

[youngnick]

Circuit breaking is a separate feature that we know we need, but yes, there is currently no GEP for that. I'll make an issue to be the place where people can register their interest now.

[youngnick]

#3358 covers circuit breaking as a feature. Note that this is just to give folks a number, not a commitment to work on this yet. That's a discussion to have during the scoping phase, which will open after Gateway API 1.2 releases.

[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