Seems to be supported [1][2]. I wonder does this feature depend on the
network plugin used in the cluster. i.e. does cluster need to use the
network policy plugin instead of the default?
[1]
https://docs.openshift.org/latest/rest_api/apis-networking.k8s.io/v1.NetworkPolicy.html
[2]
https://docs.openshift.org/3.9/rest_api/apis-networking.k8s.io/v1.NetworkPolicy.html
Łukasz Strzelec wrote on 06/18/18 15:49:
HI,
I want to have working ingress network policy based on IP BLOCK, as I
find at K8S.
Does OpenShift can do the same ? I can't find IP BLOCK definition in
API in 3.9 version.
When I declare following policy - it is not workin as suppose to work ?
How to achive the same in openshift ?
|apiVersion:networking.k8s.io/v1
<http://networking.k8s.io/v1>kind:NetworkPolicymetadata:name:test-network-policynamespace:defaultspec:podSelector:matchLabels:role:dbpolicyTypes:-Ingress-Egressingress:-from:-ipBlock:cidr:172.17.0.0/16except:-172.17.1.0/24-namespaceSelector:matchLabels:project:myproject-podSelector:matchLabels:role:frontendports:-protocol:TCPport:6379egress:-to:-ipBlock:cidr:10.0.0.0/24ports:-protocol:TCPport:5978|
Thx in advance.
--
Ł.S.
_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
