Closed sylvainOL closed 2 years ago
I know this is a weird issue and I'm more reaching for help to troubleshoot than something else
I tried to look at iptables rules created but nothing seemed weird for me
This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 180 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.
Environmental Info:
RKE2 Version:
Node(s) CPU architecture, OS, and Version:
same for all (also tested with centos 8 and ubuntu 20.04) :
Cluster Configuration: 7 servers (on VM):
Describe the bug:
When rke2 is deployed without any hardening, installation of prometheus-operator makes DNS resolution (internal and external) to stop working. With hardening (see in bottom what's meant by setting / unsetting hardening), this is working fine! Using kubespray and prometheus-operator, this is also working fine!
Steps To Reproduce:
we're using ansible playbooks to install rke2 and kubernetes services on top of it:
rke2: https://gitlab.com/Orange-OpenSource/lfn/infra/rke2_automatic_installation_collection services: https://gitlab.com/Orange-OpenSource/lfn/infra/kubernetes_collection
these are (supposed to be ;) ) reproductible builds
for rke2, here's an example of configuration files
server
agent
for prometheus, here's the override file used:
prometheus
scenarios tested
All servers are in the same (OpenStack) network.
We tried with the following OS:
We tried with the following cnis:
We tried the following versions:
We tried with and without nodelocaldns
Expected behavior:
a working kubernetes with monitoring using prometheus enabled
Actual behavior:
DNS resolution fails (DNS requests doesn't arrive on coredns pods) when prometheus operator gets installed (dns resolution is fine when not installed)
Additional context / logs:
by without hardening, I mean: without setting this:
everything is reproductible and I'm able to fire an environment to help debugging.