-
Notifications
You must be signed in to change notification settings - Fork 104
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
Feature Request: support re-deploy k8s job. #285
Comments
Can you provide the error that |
it's just like what
https://stackoverflow.com/questions/56264165/field-is-immutable-k8s
describe.
…On Fri, May 12, 2023 at 1:28 AM Oliver King ***@***.***> wrote:
Can you provide the error that k8s-deploy gives when running repeatedly?
—
Reply to this email directly, view it on GitHub
<#285 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AV7MPKFG5EYQFDGCW6V7A7TXFUOU7ANCNFSM6AAAAAAX4MPMTU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
All k8s tools I'm aware of follow the same approach that k8s-deploy used here. The stackoverflow link's solution is to delete the overlapping deployment. I'm not sure what a good way for k8s-deploy to do that would be. Deleting a resource is an extremely destructive action. |
This issue is idle because it has been open for 14 days with no activity. |
Feature request
I hope
k8s-deploy
action can support k8s job deploy repeatedly.because in normal situation, github actions will report error because of k8s job is immuteable so that we
have to delete it first.
The text was updated successfully, but these errors were encountered: