-
Notifications
You must be signed in to change notification settings - Fork 12
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
Question: dynamic flux path #278
Comments
Hi @gdlx thank you. Regarding your second question the answer is yes. Set SyncMode to "OneTime" After that, any modification to ClusterProfile won't propagate to the cluster. Regarding your first question, that is not currently possible. But I love the idea (it's very much in line with Sveltos philosophy). So I will add it. It should be easy so I can give you and image to try by end of the week. |
Change was extremely easy: projectsveltos/addon-controller#533 will create a patch release v0.29.1 |
Verified with this:
apiVersion: config.projectsveltos.io/v1alpha1
kind: ClusterProfile
metadata:
name: deploy-nginx-ingress
spec:
clusterSelector: env=fv
policyRefs:
- kind: GitRepository
name: flux-system
namespace: flux-system
path: '{{ index .Cluster.metadata.annotations "environment" }}' Sveltos instantiate path to "nginx-ingress" and deployed the content in that directory |
@gdlx this is in v0.29.1 so closing this. Please let me know if you encounter any issue. Thank you |
Thanks @gianlucam76, I'll try this ! |
Hello,
I couldn’t find this information in the documentation, so I’m not sure if it’s possible: Is there a way to dynamically set a policyRef path using the cluster env or name?
Here’s the use case: We’re currently using Flux with generated YAML files stored in a Git repository. These files are organized into directories for each environment and cluster, like so:
manifests/prod/my-prod-cluster/
I’d like to use Sveltos to push bootstrap manifests from the same source. However, the path would be different for each cluster. Therefore, I need to manage a ClusterProfile like this:
Another side question: Is it possible to use Sveltos without continuous sync to avoid conflict with FluxCD ? As I aim at using the same source repo, I'd like it to bootstrap new clusters but not to do any change once the cluster is ready.
Thanks !
The text was updated successfully, but these errors were encountered: