-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
GCE Cloud Provider: Ingress support for security policy #372
Comments
/assign cc @mdelio |
@MrHohn - any related issues created on the k8s repo ? |
@yastij There isn't yet. A relevant discussion is on kubernetes/ingress-nginx#243. |
@MrHohn @kubernetes/sig-network-feature-requests can you confirm that this feature targets 1.8? If yes, please, update the features tracking spreadsheet with the feature data, otherwise, let's remove this item from 1.8 milestone. Thanks |
@idvoretskyi This feature doesn't target 1.8 anymore, could you remove it from 1.8 milestone? Thanks. |
@MrHohn thanks |
@MrHohn @kubernetes/sig-network-feature-requests will this feature target 1.9? |
@idvoretskyi Thanks for checking. No, this feature is not targeting 1.9. |
@MrHohn @kubernetes/sig-gcp-feature-requests any plans for 1.10? |
@MrHohn - Might be able to help on this one |
@idvoretskyi @yastij Sorry for the delay. There is currently no plan for this feature for 1.10. |
@MrHohn @kubernetes/sig-gcp-feature-requests If so, can you please ensure the feature is up-to-date with the appropriate:
cc @idvoretskyi |
This feature issue is somehow obselete. Closing for now. |
Feature Description
The text was updated successfully, but these errors were encountered: