Skip to content

Conversation

christianhuth
Copy link
Contributor

  • adds Helm option to the installation docs
  • outlines a short explanation of how to use the Helm Chart to install Squest
  • links to the official documentation on ArtifactHub for more information

@Sispheor
Copy link
Contributor

Sispheor commented May 8, 2025

Hi, thanks for your PR.
We'll take a look into this proposal with the Squest team. Not sure we can reference an external project.

Technically, I'm just wondering if providing an init container for the DB initialization is working when using multiple replicas. Same for the collect statics.

@christianhuth
Copy link
Contributor Author

Hi @Sispheor
we can talk about the init container. But it's the way other project implement this step (initialize a database). What do you mean with "collect statics"?

@Sispheor
Copy link
Contributor

Sispheor commented May 9, 2025

What if multiple Django pods start in the same time and try to init the db ?

@christianhuth
Copy link
Contributor Author

I think that the first pod locks the database and the other wouldn't be able to write to the db. But I can test this.

@Sispheor
Copy link
Contributor

I can see that on the netbox project they use the same approach with an init container.
And AWX uses a job.

Also the problem may be present during the collect static command as we download in the same volume.

@Sispheor
Copy link
Contributor

Hi @christianhuth . I've received my fresh new repo for the Squest chart here.

Would you like to be the first contributor by pushing your work?

I'll then work on it to validate the deployment, add CI, markdown files, docs and probably implement the postgress support which is going to replace mariadb.

@Sispheor
Copy link
Contributor

I have identified some change to be done. Sub charts values are not taken from parent chart.
I'll propose a version.

@christianhuth
Copy link
Contributor Author

Hi @Sispheor,

yes I can contribute there. Can you add me as maintainer to the repository?

@Sispheor
Copy link
Contributor

You can PR the project directly.

I'm just wondering if we go with some of the proposed implementation.
For example, the usage of this kind of template.
From my understanding, this approach is used to supports switching between internal and potential external DBs. Netbox seems to use this as well.
Maybe the app should be fully packaged without the possibility to remove some part like mariadb. We'll see.

Copy link
Contributor

@Sispheor Sispheor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So finally, here is the plan:

  • We accept your PR as it to reference your Helm chart (Good job by the way 😉)
  • We have updated our Ansible based deployment to prepare a futur Squest K8S operator
  • The Helm repository I have mentioned will be used to deploy the operator

@Sispheor Sispheor changed the base branch from master to dev June 2, 2025 14:55
@Sispheor
Copy link
Contributor

Sispheor commented Jun 2, 2025

I've changed the target branch to dev. Conflicts appeared so I fixed them.

@Sispheor Sispheor merged commit 360a1c7 into HewlettPackard:dev Jun 2, 2025
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants