Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pipeline looks wrong: kubectl-apply-kustomize should run after pvc transfers are complete #83

Closed
jmontleon opened this issue Jun 16, 2022 · 1 comment · Fixed by #90
Closed
Assignees

Comments

@jmontleon
Copy link
Contributor

image

It appears kubectl apply and pvc transfer are happening at the same time.

The apply probably shouldn't happen until after the transfer is complete, otherwise pods may start up and try to initialize storage with new data (think like mysql or postgres setting up the db on first run) before the transfer happens.

@jmontleon
Copy link
Contributor Author

I think this more accurately reflects what we want. We basically want to add each transfer-pvc-.... to the runAfter parameter of the kubectl-apply-kustomize task.
image

@jmontleon jmontleon changed the title Pipeline looks wrong Pipeline looks wrong: kubectl-apply-kustomize should run after pvc transfers are complete Jun 16, 2022
@jmontleon jmontleon transferred this issue from migtools/crane-operator Jun 16, 2022
@djzager djzager self-assigned this Jun 24, 2022
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 a pull request may close this issue.

2 participants