feat: bootstrap new instances with an init container instead of a separate Job - #11319
Open
leonardoce wants to merge 1 commit into
Open
feat: bootstrap new instances with an init container instead of a separate Job#11319leonardoce wants to merge 1 commit into
leonardoce wants to merge 1 commit into
Conversation
leonardoce
marked this pull request as ready for review
August 13, 2026 08:04
cnpg-bot
added
backport-requested ◀️
leonardoce
requested review from
a team,
NiccoloFei,
jsilvela and
litaocdl
as code owners
August 13, 2026 08:04
Contributor
|
❗ By default, the pull request is configured to backport to all release branches.
|
dosubot
Bot
added
size:L
leonardoce
added
do not backport
Contributor
Author
|
/test bp=pr-1025 l=kind |
Contributor
|
@leonardoce, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/31681054762 |
armru
approved these changes
Aug 13, 2026
…arate Job New primary and replica instances are now bootstrapped (initdb, recovery, pg_basebackup, join, and snapshot restore) directly on the instance Pod via an init container, instead of running a separate Kubernetes Job beforehand. This removes the extra Job resource previously created for every new instance, along with its own Pod, and the wait for that Job to complete before the actual instance Pod could start. Signed-off-by: Leonardo Cecchi <leonardo.cecchi@enterprisedb.com>
leonardoce
force-pushed
the
remove-jobs-initcontainer
branch
from
August 17, 2026 08:51
cb78fa2 to
4987ac8
Compare
Contributor
Author
|
/test bp=pr-1025 l=kind |
Contributor
|
@leonardoce, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/32012769354 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New primary and replica instances are now bootstrapped (initdb, recovery,
pg_basebackup, join, and snapshot restore) directly on the instance Pod via
an init container, instead of running a separate Kubernetes Job beforehand.
This removes the extra Job resource previously created for every new
instance, along with its own Pod, and the wait for that Job to complete
before the actual instance Pod could start.
Closes: #11228
Important
This is an alternative approach for #11231 that is less invasive on the codebase.
It requires #11315 to be merged too.