-
Notifications
You must be signed in to change notification settings - Fork 14
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
Updating k8s pod and container templates with no host ips and realistic hostnames #111
Conversation
"fe80::5d:14ff:fec1:2d3a" | ||
], | ||
"name": "{{ $agentName }}", | ||
"name": "{{- $nodeid := generate "nodeid" -}}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
beware, if you invoke generate "nodeid"
two times in the same template you should end up with two different values
you should: because looking at the screenshot you posted it does not seems so, but this is something to investigate, since it seems to be bug :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok once per file. Then I refer to nodeid variable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the host name doesn't need to be to same as node name? As long as each node name uses the same host name?
@@ -103,12 +104,12 @@ | |||
}, | |||
"node":{ | |||
"uid": "{{ $uId }}" , | |||
"hostname":"{{ $agentName }}.c.elastic-obs-integrations-dev.internal", | |||
"name":"{{ $agentName }}-{{ $rangeofid }}", | |||
"hostname":"node-{{ $nodeid }}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe host-{{ $nodeid }}
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
@@ -214,7 +215,7 @@ | |||
"dataset":"kubernetes.container" | |||
}, | |||
"host":{ | |||
"hostname":"{{ $agentName }}", | |||
"hostname":"node-{{ $nodeid }}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe host-
?
@@ -28,12 +29,12 @@ | |||
"kubernetes": { | |||
"node":{ | |||
"uid": "{{ $uId }}" , | |||
"hostname":"{{ $agentName }}.c.elastic-obs-integrations-dev.internal", | |||
"name":"{{ $agentName }}-{{ $rangeofid }}", | |||
"hostname":"node-{{ $nodeid }}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe host-
?
@gizas could you please move the files of each folder inside the |
…generator-tool into update_k8s_pod_container_templatesforTSDB
@@ -45,7 +45,7 @@ fields: | |||
- name: container.name | |||
enum: ["web", "default-http-backend", "dnsmasq", "csi-driver", "web", "web", "web", "prometheus", "konnectivity-agent", "sidecar", "kubedns", "metrics-server-nanny", "web", "web", "fluentbit", "autoscaler", "gke-metrics-agent", "elastic-agent", "web", "kube-state-metrics", "metrics-server", "fluentbit", "elastic-agent", "web", "prometheus-to-sd-exporter"] | |||
- name: timedate | |||
# Add more dates below in case you want your data to be spread | |||
# Add more dates below in case you want your data to be spread.Those are fixed because this is required in the nightly tests of Rally |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you explain about this?
will it be fixed "forever", or only for the current nightly tests of rally.
what happens if we use timestamp
with period: 2880m
(two days) like I did here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one is fixed for the current nightly tests of rally. We have specific visualisations and we want our data to be in specific range in order our queries to be be always specific
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would it be possible to change the visualisation range to be -2d/now
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aspacca
I have made some tests today and from generator tool side we can change the timedate to date type with [period: 48h] and all seem ok. So I dont see an issue with this now
Moreover on the rally side we have hardcoded the values of visualisations here
So we need to find a way to import to calculate the new itervals and end_time based on the track provided.
cc @martijnvg for visibility
…s based on pod rangeofid div 110
I assume eventually we will move these files over to the k8s package? |
@aspacca and @martijnvg I think this can also be merged now as it has been tested in various places and different PRs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
…generator-tool into update_k8s_pod_container_templatesforTSDB
TSDB nightly tests demand a more realistic set of data generated. As part of this enhancement we update kubernetes pod and container templates with following:
How to test:
Check that host.ips and host.mac fields are removed
Check the node names created and have the same value as hostnames.
Screenshot