API Graduation Criteria (Alpha to Beta) and Open Questions

[tssurya]

Firstly, do we plan to have v1alpha2 and then move to beta or do we want to go straight to beta?

Checklist of items before graduation to beta (if we decide to do some of this in v1alpha2 itself, then we can move them over to that accordingly): https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2091-admin-network-policy#graduation-criteria

• Gather feedback from developers and surveys

• ONGOING

• At least 2 implementors must provide a functional and scalable implementation for the complete set of alpha features.

• Add Support for Admin Network Policy ovn-kubernetes/ovn-kubernetes#3489 - ONGOING

• Conformance tests

TODO; can happen only when we have a successful implementation.

• Evaluate the need for multiple Subjects per ANP.

This was brought up in the sig-network-policy-api meeting on March 14th; see the meeting notes/video recording

• Evaluate "future work" items based on feedback from community and challenges faced by implementors.
• Ensure extensibility of adding new fields. i.e. adding new fields do not "fail-open" traffic for older clients.
• Revisit the topic of whether this API should cover north-south traffic.

IMHO we should do this in alpha itself
ONGOING, see #86

• Scale? -> can we make this beta to GA criteria?
• What else?

[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

[k8s-triage-robot]

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

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.

[tssurya]

/reopen

[k8s-ci-robot]

@tssurya: Reopened this issue.

In response to this:

/reopen

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-sigs/prow repository.

[tssurya]

/remove-lifecycle rotten