Support N MongoDB shards

[williamlardier]

Here, we only support deployment of multiple shards. Upgrades is managed by upper layers for now.

Issue: ZENKO-4641

[bert-e]

Hello williamlardier,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

[williamlardier]

Note for reviewers: this was removed because we had this logic twice in the function, maybe a rebase issue at some point. See above.

[francoisferrand]

this does the same as the original kustomize, with a few differences:

• handles multiple shards seamlessly (as was your goal i guess)
• does not overwrite/set the storageclass to standard (not sure if it is needed)
• does not set the requested storage to 8Gi (how much gets requested? is it enough?)

[williamlardier]

The base has 10Gi, which is enough, no need to change it.

does not overwrite/set the storageclass to standard (not sure if it is needed)

It's done but elsewhere (it was the case already before, we were doing it twice):

    sed -i 's/MONGODB_STORAGE_CLASS/standard/g' $DIR/_build/root/deploy/*

handles multiple shards seamlessly (as was your goal i guess)

yes!

[williamlardier]

Added a commit to remove the matchLabel for the shard0, so that we do not require any downtime during shard expansion.