-
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
[kpt deployer] Add "local-config" annotation to kpt fn configs. #4803
[kpt deployer] Add "local-config" annotation to kpt fn configs. #4803
Conversation
The `config.kubernetes.io/local-config:true` annotation will skip the kpt fn resource from deploying to the cluster in `kpt live apply`.
0fa7e0a
to
6ebae64
Compare
/assign @MarlonGamez |
Codecov Report
@@ Coverage Diff @@
## master #4803 +/- ##
==========================================
- Coverage 71.82% 71.62% -0.21%
==========================================
Files 347 348 +1
Lines 11869 12051 +182
==========================================
+ Hits 8525 8631 +106
- Misses 2725 2781 +56
- Partials 619 639 +20
Continue to review full report at Codecov.
|
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.
Looks good, just have a suggested fix for the imports and a small nit
15e1a78
to
ade595c
Compare
ade595c
to
4e60daf
Compare
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.
Looks good!
Related #3904
Description
Add a
config.kubernetes.io/local-config:true
annotation to each kpt fn config from the rendered resources. This allows kpt deployer to skip deploying the kpt fn config to the cluster inskaffold dev
andskaffold deploy
.more context: The declarative kpt fn is not config resource but an operation working on the resource. It should not be applied to the cluster. Applying the kpt fn to cluster could fail due to the different config requirements (e.g. kpt fn ConfigMap doesn't require the
.metadata.name
field to exist while normal ConfigMap does).