Enhancements: ipBlock for Network Policies

[cmluciano]

Feature Description

• One-line feature description (can be used as a release note):
  
  
  
  • CIDR selector support for egress/ingress network policies
  
  
• Primary contact (assignee): @cmluciano
• Responsible SIGs: SIG-Network
• Design proposal link (community repo): kubernetes/kubernetes#49978
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @caseydavenport @danwinship
• Approver (likely from SIG/area to which feature belongs): @thockin
• Feature target (which target equals to which milestone):
  
  
  
  • Beta release target (1.8)
  
  
  • Stable release target (1.11)
  
  

[cmluciano]

code complete in https://github.com/kubernetes/kubernetes/pull/50033.

TODO:

• [ ] More e2es
• [ ] Docs

[jdumars]

@cmluciano any update on missing docs? The PR is due today.

[jdumars]

@caseydavenport @cmluciano mentioned you as the contact for docs. We need them ASAP in order to make the 1.8 release docs.

[caseydavenport]

Docs PR is here: https://github.com/kubernetes/kubernetes.github.io/pull/5529

[cmluciano]

Docs fixed in https://github.com/kubernetes/kubernetes.github.io/pull/5473

[cmluciano]

this was merged for 1.8

[cmluciano]

reopening for tracking stable

[idvoretskyi]

@cmluciano @kubernetes/sig-network-feature-requests still on track for 1.10?

[cmluciano]

This is still under discussion in the mailing list.

[idvoretskyi]

@cmluciano any progress?

[cmluciano]

Yes, from our mailing list conversations this feature with not GA in 1.10. We will continue discussing potential for future releases on the sig-network mailing list.

[idvoretskyi]

@cmluciano got it, will mark with 1.10 milestone and keep beta for now.

PS. The same is for https://github.com/kubernetes/features/issues/366#issuecomment-359450296

[idvoretskyi]

@cmluciano also updated the description to plan GA for 1.11 (for both features). Correct me if I wrong.

[cmluciano]

There is ongoing discussion on NetworkPolicy as a whole. Can we hold off on marking a stable milestone until these conversations conclude?

[idvoretskyi]

@cmluciano please, do.

[justaugustus]

@cmluciano
Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

• Description
• Milestone
• Assignee(s)
• Labels:
  
  
  
  • stage/{alpha,beta,stable}
  
  
  • sig/*
  
  
  • kind/feature
  
  

cc @idvoretskyi

[justaugustus]

This feature current has no milestone, so we'd like to check in and see if there are any plans for this in Kubernetes 1.12.

If so, please ensure that this issue is up-to-date with ALL of the following information:

• One-line feature description (can be used as a release note):
• Primary contact (assignee):
• Responsible SIGs:
• Design proposal link (community repo):
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
• Approver (likely from SIG/area to which feature belongs):
• Feature target (which target equals to which milestone):
  
  
  
  • Alpha release target (x.y)
  
  
  • Beta release target (x.y)
  
  
  • Stable release target (x.y)
  
  

Set the following:

• Description
• Assignee(s)
• Labels:
  
  
  
  • stage/{alpha,beta,stable}
  
  
  • sig/*
  
  
  • kind/feature
  
  

Once this feature is appropriately updated, please explicitly ping @justaugustus, @kacole2, @robertsandoval, @rajendar38 to note that it is ready to be included in the Features Tracking Spreadsheet for Kubernetes 1.12.

---

Please note that Features Freeze is tomorrow, July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.

In addition, please be aware of the following relevant deadlines:

• Docs deadline (open placeholder PRs): 8/21
• Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.

Happy shipping!

P.S. This was sent via automation

[danwinship]

doh, we did all of the discussion for this feature on the egress PR (#366) and forgot to update this PR as well.

Let's see if this still works:

/milestone v1.12
/remove-stage beta
/stage stable

[danwinship]

@justaugustus, @kacole2, @robertsandoval, @rajendar38 This was supposed to have been tracked for 1.12 but we basically forgot that we had two separate feature PRs. All of the work is done, including tests and docs.

[danwinship]

(ping @cmluciano)

[kacole2]

@danwinship I've got ahead and added this to the tracking sheet after seeing @tpepper +1 on the exception filed.

[danwinship]

@kacole2 Thanks! It probably should have milestone v1.12 too?

[kacole2]

@danwinship it should but I don't have those powers yet.
@justaugustus can you add the correct labels?

[justaugustus]

Fixed!
/milestone v1.12

[kacole2]

/close

[k8s-ci-robot]

@kacole2: Closing this issue.

In response to this:

/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.