inside different project as i mentioned before.
I tried to allow access only using podSelector without namespaceSelector, but
still without success.
Is there are any workaround or solution to allow/restrict access between
different projects/namespaces specific pods labels?
--
Best,
Alexander
Wow,
Thanks a lot Samuel !! I did not know that. And yes, thought they are working
same way as kubernetes networkpolicies. I tried out EgressNetworkPolicy AND IT
WORKS!!
You saved my day...Thanks a lot.
--
Best,
Alexander Kozhemyakin
From: Samuel Martín Moro
Date: Wednesday, 27 March 2019
what should i check or do? Are they
supported in this openshift version?
Thank’s in advice..
--
Best,
Alexander Kozhemyakin
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Yeah, i did not included in installiation grafana, hawkular etc. I have ELK
stack with okd integration..
I setup cluster on CentOS 7.5 with checked out openshift-ansible playbook’s
repo “release-3.11” and inventory file looks like this (attached text file).
--
Best,
Alexander Kozhemyakin
ods
cat: /etc/sysconfig/KUBELET_HOSTNAME_OVERRIDE: No such file or directory
node "dca-infra1" annotated
I also googled a little bit, but without success finding the real issue here..
This comes with fresh install...
Does anybody faced similar issue?
Thanks a lot!
--
Best,
