[Docker] Build Container for Microservice Deployment. #54
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
surahman
force-pushed
the
features/docker-image-build-and-container-prep
branch
from
4a52d6a to
53de81a
Compare
surahman
force-pushed
the
features/docker-image-build-and-container-prep
branch
from
c7cbe7f to
168bd80
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a Docker container build script. Please see the details included in the Readme file.
It is vital to set the processor count to reflect the CPU resources provided by Kubernetes in the Deployments. By using the
go.uber.org/automaxprocspackage, Go will detect the Pod's CPU allocation and not the Kubernetes cluster's host CPU resources. This means that the Go runtime's thread scheduler will schedule threads at more optimal quantums based on the Pod's resources.