This repository was archived by the owner on Aug 4, 2020. It is now read-only.
MGMT-1667: Use minikube profile per namespace#525
Open
Conversation
We want to be able to deploy more then one environment on the same host, using minikube. In order to support initializing and destroying of a deployment without effecting the rest of the environments we will use minikube profile per deployment. By default, if no profile is specified, deploy services to default 'minikube' namespace.
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We want to be able to deploy more then one environment on the same host,
using minikube. In order to support initializing and destroying of a deployment
without effecting the rest of the environments we will use minikube profile
per deployment. By default, if no profile is specified, deploy services to
default 'minikube' namespace.