[Demo with Kustomize] Add missing ServiceAccount of color-svc #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Overview
This fixes Kubernetes Deployment of
color-svc
, which uses ServiceAccount ofcolor-svc
but was missed in the setup.Challenges
🤔 Easy to Miss in
kustomization.yaml
Kustomize needs to explicitly list all the resources. This is a useful design and certainly has its own merit, but it also means you can end up with new resource files created without actually having any effect.
Because there is nothing wrong in the spec, it can be surprisingly difficult to spot how the new resource does not show up.
Solutions
🎯 Additional Tooling (no example here)
(As of Sep 2021)
There are useful tools like dyff, which is a CLI tool to view the diff between two YAML inputs. However, it has this limitation that it cannot show the diff if the number of documents in YAML does not match in those 2 files.
If this type of change is common, you'd need some other automation, perhaps even using
sdiff
againstkustomize build
output.