You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 5, 2023. It is now read-only.
... which has the following flaws:
a) the name needs to be specified (causes an Service \"svc-default-k8s-appcoredns\" is invalid: [spec.ports[0].name: Required value, spec.ports[1].name: Required value]), as the target-port is the same, right?
b) protocol UDP gets translated to TCP (not sure if that's an issue)
Also, with my cluster I ran into the test_orchestrator.py ValueError:
Only ClusterHost and GenericClusterHost fromHosts are supported by this Orchestrator
Can I simply put a continue instead, in order to skip the cases where I might reference an external host (we have a few headless services; might those cause issues?) ?
Last but not least, Illuminatio seems to not fully clean up its resources. After running clean, I still saw dummy pods in kube-system namespace, and a service called "svc-kube-system-appnet-exporter" etc.
Nonetheless, great tool! Wish I could make it work on our cluster :)
The text was updated successfully, but these errors were encountered:
When mapping the following service ...
... illuminatio breaks, as it translates it into:
... which has the following flaws:
a) the name needs to be specified (causes an
Service \"svc-default-k8s-appcoredns\" is invalid: [spec.ports[0].name: Required value, spec.ports[1].name: Required value]
), as the target-port is the same, right?b) protocol UDP gets translated to TCP (not sure if that's an issue)
Also, with my cluster I ran into the test_orchestrator.py ValueError:
Can I simply put a
continue
instead, in order to skip the cases where I might reference an external host (we have a few headless services; might those cause issues?) ?Last but not least, Illuminatio seems to not fully clean up its resources. After running
clean
, I still saw dummy pods in kube-system namespace, and a service called "svc-kube-system-appnet-exporter" etc.Nonetheless, great tool! Wish I could make it work on our cluster :)
The text was updated successfully, but these errors were encountered: