Add --opencost
flag to setup standard OpenCost configuration
#173
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.
What does this PR change?
This Pull Request adds the
--opencost
flag to the cost command to setup standard OpenCost configuration. It is essentially an alias for the following flags:--service-port 9003 --service-name opencost --kubecost-namespace opencost --allocation-path /allocation/compute
Does this PR rely on any other PRs?
N/A
How does this PR impact users? (This is the kind of thing that goes in release notes!)
The user will have the possibility to easily set OpenCost as the target service to the
kubectl cost
command by simply setting the--opencost
instead of configuring the OpenCost default settings flag-by-flag.Links to Issues or ZD tickets this PR addresses or fixes
--opencost
flag to specify standard OpenCost settings #156How was this PR tested?
This Pull Request was tested in an Oracle Kubernetes Engine (OKE)-based Kubernetes cluster configured with OpenCost and identical behaviour with providing the following flags was asserted:
--service-port 9003 --service-name opencost --kubecost-namespace opencost --allocation-path /allocation/compute
Have you made an update to documentation?
An update was made in the README.md file.