https://signoz.io logo
#contributing
Title
# contributing
r

Raj Das

10/03/2021, 6:12 AM
Hi @User, Any plans to creating a repo for signoz helm charts? I can work on that, if you want.
a

Ankit Nayan

10/03/2021, 6:16 AM
@User we are working on creating helm charts for clickhouse..and we will also evaluate creating separate repo for deployment/helm charts.
👍 1
@User is looking into this. @User Would you be interested in discussing the pros and cons over a call say Wed sometime?
r

Raj Das

10/03/2021, 6:21 AM
Sure, We can discuss on Wednesday.
a

Ankit Nayan

10/03/2021, 6:22 AM
does 12pm/1pm/4pm work? suggest a time
and your email? will send an invite
r

Raj Das

10/03/2021, 6:28 AM
4pm works for me. Here is my mail- mail.rajdas@gmail.com
Hi @User, Let me know about your decision on the helm charts thing, I can set up the pipeline to deploy the signoz charts to github pages.
a

Ankit Nayan

10/07/2021, 12:00 PM
@User I think the above setup to deploy by gh-pages is independent to adding clickhouse setup to the current helm chart? If so, can @User work on deploying the signoz charts to github pages. Or we can wait for a week if we need more time 🙂
a

Abhishek Sehgal

10/07/2021, 12:25 PM
yeah, we can work on it independently. Whenever we are ready with clickhouse-setup helm chart, we will upload it there
r

Raj Das

10/07/2021, 12:38 PM
Okay, so, we will use the current signoz repo for helm charts Right?
a

Ankit Nayan

10/07/2021, 2:54 PM
yes..we can keep that for now..the steps should be easy to move in new repo also right?
a

Abhishek Sehgal

10/07/2021, 3:23 PM
Would be better to have it in a different repo? Where we can have all the deployment specific things including install scripts or other form of deployments. In that we can have github pages as well. Reason being if we need different branches for versioning, may be we just need to have them for deployment purpose, not for signoz main repo. Thoughts?
a

Ankit Nayan

10/07/2021, 5:15 PM
ok...does the new repo versioning work independent of core versioning? If so, when we say a feature X is released, the core repo would say it is released in say 1.3.0 but if devs want to use it they need to deploy helm version 1.9.x? Won't this be confusing?
Also, say the new repo has deployments of multiple ways -> docker-compose, swarm & helm. Will a tag in the repo be same for all (meaning all will upgrade together) or will they have independent versions?
Another scenario, let's assume aws and gcp deployments in vms are maintained in different folders in the new repo. When a feature is ready to be released in aws but not in gcp, how will this be faciliated in repo versions/releases?
a

Abhishek Sehgal

10/08/2021, 3:15 AM
Good points Ankit. will go through these repos today. Let's create a doc for all these and other points. I will write all these points and share it here. Then we can do the discussion and get the conclusion there.
💯 1
a

Ankit Nayan

10/13/2021, 4:01 PM
Can we dig deeper this weekend?
👍 2
@User You can have a look at this conversation too
👍 1
2 Views