This I think was the wrong assumption I also made. A attacked this problem
mainly from another angle because I was trying to template this all in Helm
keeping things namespace generic.
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and
I also find it very interesting that Network Policy API requires namespaces
to be labeled, rather than working with namespace names directly.
I wonder who out there is actively labeling their namespaces, but it sounds
like a good practice and a good use case for labels.
I have some off the shelf
I also made the same incorrect assumptions. Thanks for identifying it, I
will also give it a try.
many kind regards,
Andrew
On Monday, April 30, 2018 at 8:34:13 AM UTC+2, Mark NS wrote:
>
> Gah, I could kick myself!
>
> I was expecting that
>
> - from:
> - namespaceSelector:
> m
Gah, I could kick myself!
I was expecting that
- from:
- namespaceSelector:
matchLabels:
name: kube-system
would match
kind: Namespace
metadata:
name: kube-system
Which of course it won't... only when the label name: kube-system is applied
kind: Namespace
metadata
Hi,
I also seem to be unable to configure a network policy to allow pod ingress
only from an nginx ingress-controller
Here is what I did (GKE 1.8.8-gke.0):
$ kubectl run web --image=gcr.io/google-samples/hello-app:1.0 --port=8080
$ kubectl expose deployment web --target-port=8080 --type=NodePort
When editing an already published network policy the namespace field is
automatically populated.
On Saturday, March 10, 2018 at 1:13:24 AM UTC+1, Igor Cicimov wrote:
>
> This is missing `namespace:` in metadata
--
You received this message because you are subscribed to the Google Groups
"Kuber
Hi,
I was not able to make any progress here. I have to disable the network policy
for services that should be reached by the ingress controller as a workaround.
kind regards,
Andrew
On Thursday, March 1, 2018 at 6:12:26 PM UTC+1, i...@ciklum.com wrote:
> On Wednesday, July 19, 2017 at 5:53:1
On Wednesday, July 19, 2017 at 5:53:18 PM UTC+3, mrpanigale wrote:
> I am unable to define a network policy that allows an ingress controller
>
>
> Example:
>
>
> Pod in namespace A
> Ingress controller in namespace kube-system
>
>
> Policy:
>
> kind: NetworkPolicy
> apiVersion: networking.k
