Date
1 - 3 of 3
Complex charts
|
j.g.pelham@...
Yes numerous services. I have two objectives. One is to make software in loop testing of drones more reproducible and the other is to create a scalable system to study network interaction. Hopefully integrate it with ROS at some
point as well. Some nodes quite compute intensive but the network has the most load.
It would probably be an MIT license or one of the open ones. Do you know of anything anyone has done which has any similarity which I could look at?
Joni
From: cncf-helm@... <cncf-helm@...> on behalf of Matt Farina <matt@...>
Sent: Tuesday, August 13, 2019 5:20:09 PM To: cncf-helm@... <cncf-helm@...> Subject: Re: [cncf-helm] Complex charts Hi Joni.
Is this flight simulation system one application with numerous microsevices? If so, it may make sense to do it as a single chart. That's what I would do.
Are you going to share this chart publicly or keep it private? If you are going to keep it private it may make sense to use a single chart. If it's public and uses some common components (e.g., mariadb or postgresql) it may make sense to depend on another
chart for one of those.
One flat chart with some templating is fine to do.
Hope that helps
- Matt Farina
On Tue, Aug 13, 2019, at 2:50 AM, j.g.pelham@... wrote:
|
|
|
|
Matt Farina
Hi Joni. Is this flight simulation system one application with numerous microsevices? If so, it may make sense to do it as a single chart. That's what I would do. Are you going to share this chart publicly or keep it private? If you are going to keep it private it may make sense to use a single chart. If it's public and uses some common components (e.g., mariadb or postgresql) it may make sense to depend on another chart for one of those. One flat chart with some templating is fine to do. Hope that helps - Matt Farina On Tue, Aug 13, 2019, at 2:50 AM, j.g.pelham@... wrote:
|
|
|
|
j.g.pelham@...
Hi All, I was advised to ask here regarding complex helm chart development. I'm trying to put together a new flight simulation system and this means a lot of inter-node communication through things like sockets. Maybe also some WebRTC further down the line. Maybe one flat chart with some templating to automate the notation required for what is linking to what? Has anyone tried this sort of thing before?
Kind regards Joni |
|
|