-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Netreap dont be reapplying the labels #20
Comments
I noticed such a moment, when starting a nomad-job with several groups, only one of the groups receives the label.
Cilium endpoint list:
Netreap-job logs:
The second group remains in the init state. But if I restart Netreap in the cluster, both groups will immediately get the label.
Netreap-job logs:
Maybe this is a bug or am I doing something wrong? In my cases, nomad jobs most often consist of several groups. Please take a look @deverton @protochron Netreap - 0.1.2 also 0.1.0 |
Before host restart:
After host restart:
Netreap dont be reapplying the labels after restart host.
Netreap debug logs:
In some cases, some jobs re-tagged, but not all:
In order for jobs to get tags again, and sometimes ip, you need to stop & start the job again:
Before restart job:
After restart job:
Netreap logs:
Cilium & Neatreap deployed from this guide https://cosmonic.com/blog/engineering/netreap-a-practical-guide-to-running-cilium-in-nomad. I think that this behavior of netreap is not entirely correct. Please tell me what is the reason for this behavior and how can I fix it? @deverton @protochron
Cilium - v1.13.4
Netreap - v0.1.0
The text was updated successfully, but these errors were encountered: