You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
Perform cluster-sync locally and see the config/manager/kustomization.yaml file is changed.
It isn't good because it makes us have an unstaged file that makes working with git locally
less convenient.
What you expected to happen:
We should find a solution that doesnt alter files (at least not tracked ones) when we cluster-sync locally.
How to reproduce it (as minimally and precisely as possible):
Just run cluster-sync locally and see git status.
Additional context:
Environment:
KubeVirt version (use virtctl version): N/A
Kubernetes version (use kubectl version): N/A
VM or VMI specifications: N/A
Cloud provider or hardware configuration: N/A
OS (e.g. from /etc/os-release): N/A
Kernel (e.g. uname -a): N/A
Install tools: N/A
Others: N/A
The text was updated successfully, but these errors were encountered:
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
What happened:
Perform cluster-sync locally and see the
config/manager/kustomization.yaml
file is changed.It isn't good because it makes us have an unstaged file that makes working with git locally
less convenient.
What you expected to happen:
We should find a solution that doesnt alter files (at least not tracked ones) when we cluster-sync locally.
How to reproduce it (as minimally and precisely as possible):
Just run cluster-sync locally and see git status.
Additional context:
Environment:
virtctl version
): N/Akubectl version
): N/Auname -a
): N/AThe text was updated successfully, but these errors were encountered: