-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Kustomize deployer mutations #1395
Comments
I raised this over at the Kustomize project a while ago and got some good suggestions: kubernetes-sigs/kustomize#164 Maybe the answer is just "use the kustomize CLI to preprocess the YAML appropriately", but wondering if you have different ideas. |
skaffold actually uses
is that enough to address your use case? another option would be to go the env var route, but we try to avoid that whenever possible :) |
This is interesting, for ephemeral environments we don't have a good answer for this. As we discussed with @nkubala we could do something like @paultiplady is this still an issue? |
this one has gone stale, and I'm not entirely sure what the path forward would be here. realistically, our team isn't gonna be able to put any work into this any time soon, and since it doesn't seem to be causing too much of an issue, I'm going to close it. if this is still causing you issues in your daily skaffold workflow, please react to this comment and give us more details on your use case! |
Support for |
Expected behavior
It should be possible to configure the namespace of the kustomization dynamically.
Actual behavior
It appears there is no way to configure the namespace dynamically in a Kustomization.
Information
A common pattern for deploying k8s apps is to use a namespace per deploy. Another alternative is to use name prefixes inside a single namespace.
Both of these options are supported in Kustomize using the
kustomize edit set namespace|nameprefix
commands.I don't see a way to achieve this effect in Skaffold. The best I can do is
but this fixes the namespace, rather than allowing it to be configured dynamically by the build environment (e.g. based on a PR slug).
This is certainly a feature request, but it's also not clear exactly what the best approach here would be.
The text was updated successfully, but these errors were encountered: