updated to get information from kubernetes API instead of downward API and support one namespace per application. #3
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.
@ustudio/dev please review
As we discussed, we need to update the library to support one namespace per application and one cluster per namespace. Because there is no way to get cluster-wide information from the Downward API we need to access it via the Kubernetes API.
Since we were already using the Kubernetes API we removed the dependence on the Downward API and now access all information via the Kubernetes API. This has the added benefit of requiring no special configuration of the pod to use the library.
We decided to store the
environment-info
secret in theustudio-system
namespace where we were already running the SumoLogic and DataDog integrations.This change is