-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add 'skaffold apply' command #5543
Conversation
93620ed
to
e72ebcc
Compare
Codecov Report
@@ Coverage Diff @@
## master #5543 +/- ##
==========================================
- Coverage 71.22% 71.07% -0.16%
==========================================
Files 400 402 +2
Lines 14934 15055 +121
==========================================
+ Hits 10637 10700 +63
- Misses 3510 3563 +53
- Partials 787 792 +5
Continue to review full report at Codecov.
|
}, doApply) | ||
} | ||
|
||
func doApply(ctx context.Context, out io.Writer, args []string) error { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should you allow glob
arguments like kubectl
deployer currently does?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we support urls?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we support reading from STDIN
so I could do this 😅:
In examples/multi-config-microservices
skaffold diagnose --yaml-only | skaffold render -f - | skaffold apply -
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
haha yes these are all great suggestions 😄 i think i'm fine with supporting all 3 of these, but how about i add them in a follow up PR? they seem like QOL enhancements to this feature
forgot to mention, docs are on their way |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed some passive voice
Co-authored-by: Brian de Alwis <bsd@acm.org>
Co-authored-by: Brian de Alwis <bsd@acm.org>
Co-authored-by: Brian de Alwis <bsd@acm.org>
Co-authored-by: Brian de Alwis <bsd@acm.org>
CI is failing because of a docker rate limit issue:
|
codecov is reporting some very strange results: https://app.codecov.io/gh/GoogleContainerTools/skaffold/compare/5543/changes going to self-merge since the rest of CI is green. |
This change adds a new command,
skaffold apply
, which accepts one or more hydrated Kubernetes manifests and uses them to create resources on the cluster.skaffold apply
does not perform any build actions (skaffold build
), and does not perform any configuration management (skaffold render
): it instead blindly consumes whatever Kubernetes configuration it is passed and sends it tokubectl
. It will, however, monitor resource status through the built-instatus-check
mechanism.This command unlocks the ability for Skaffold to consume its own output from
skaffold render
:Skaffold labels
skaffold.dev/run-id
andkubernetes.io/managed-by
will be added to all deployed resources since they are required by the status checker. cc #5542To be merged after #5541 - please review that PR first, and this change will be rebased for ease of review once that PR is merged.
Part 2 / Fixes #4856