docs: remove incorrect statement about BuildKit deployment name #2413
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 issue type does this pull request address? (keep at least one, remove the others)
/kind documentation
What does this pull request do? Which issues does it resolve?
A user was attempting to manage the BuildKit Daemon using instructions from this repo in order to increase replicas and use a Horizontal Pod Autoscaler. However, the
buildctl
command is not supported by DevSpace, and our docs were misleading in that the Deployment created for the BuildKit Daemon would match the name given in theinCluster.name
option.Instead, this name is passed to
docker buildx create --driver kubernetes
which creates a deployment with a different name, usually${inCluster.name}0
. There is not an option to directly control the deployment name.Please provide a short message that should be published in the DevSpace release notes
Fixed misleading documentation about BuildKit Daemon deployments
What else do we need to know?
Recommended that the user create the builder with
docker buildx create --driver kubernetes --bootstrap
and use the generated manifests as a starting point for their customizations.