Enable multiple deployers in skaffold.yaml#3392
Enable multiple deployers in skaffold.yaml#3392dgageot merged 10 commits intoGoogleContainerTools:masterfrom
skaffold.yaml#3392Conversation
|
I went with the approach to simply drop the deploy:
kubeContext: something
deployers:
- kustomize: {}
- kubectl: {}
- helm: {}
- ...However, the nested |
Codecov Report
|
skaffold.yamlskaffold.yaml
512a92f to
d746cfc
Compare
This allows re-use by other deployer renderers. Signed-off-by: Cornelius Weig <22861411+corneliusweig@users.noreply.github.com>
This Deployer implemenation forwards commands to all of the deployers in his list. It will be useful to allow multiple deployers in skaffold.yaml. Signed-off-by: Cornelius Weig <22861411+corneliusweig@users.noreply.github.com>
Signed-off-by: Cornelius Weig <22861411+corneliusweig@users.noreply.github.com>
Some use-cases require a hybrid mode where users need to use different deployers at the same time. Signed-off-by: Cornelius Weig <22861411+corneliusweig@users.noreply.github.com>
So far, deployers were marked with `oneOf`, so that only one of them could be active at a time. Since this no longer holds, profile activation now merges the deployers from profiles and base. This change adapts the tests accordingly. Signed-off-by: Cornelius Weig <22861411+corneliusweig@users.noreply.github.com>
This is necessary because the new logic merges profile deployer into the main pipeline instead of replacing existing deployers. Signed-off-by: Cornelius Weig <22861411+corneliusweig@users.noreply.github.com>
Signed-off-by: Cornelius Weig <22861411+corneliusweig@users.noreply.github.com>
Signed-off-by: Cornelius Weig <22861411+corneliusweig@users.noreply.github.com>
d746cfc to
ec3eaf0
Compare
skaffold.yamlskaffold.yaml
|
I've finally added the missing integration test, so it's no longer WIP :) |
| controls how Skaffold builds artifacts. To use a specific tool for deploying | ||
| artifacts, add the value representing the tool and options for using the tool | ||
| to the `deploy` section. | ||
| to the `deploy` section. You may even use different tools at the same time. |
There was a problem hiding this comment.
| to the `deploy` section. You may even use different tools at the same time. | |
| to the `deploy` section. You may even use a combination of each available deployment approach at the same time. |
There was a problem hiding this comment.
I'll not apply this suggestion right now, to not interfere with the kokoro run. But please go ahead and apply this if you think it's ready for merging!
There was a problem hiding this comment.
I just pushed it - will merge as soon as kokoro is done again :)
|
I just rebased it - hope that's fine! |
Yes of course! |
Relates to #2875, #3292
Fixes #2875, #3292
Should merge before : n/a
Should merge after : #3391,
#3390Description
Some users find it limiting that they can only configure a single deployer in Skaffold (#2875, #3292). This PR enables using multiple deployers.
User facing changes
Users get the possibility to configure multiple deployers.
Before
skaffold.yamlallows to configure exactly one deployer (kubectl,kustomize,helm).After
Users can configure all three deployers at once. Iow, the
oneOf=deployerconstraint inskaffold.yamlis dropped.Next PRs.
n/a
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
Reviewer Notes
Release Notes