Skip to content
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

Kustomize file is changed on cluster-sync #58

Open
oshoval opened this issue Aug 19, 2024 · 1 comment
Open

Kustomize file is changed on cluster-sync #58

oshoval opened this issue Aug 19, 2024 · 1 comment
Labels
kind/bug lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@oshoval
Copy link
Collaborator

oshoval commented Aug 19, 2024

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
@kubevirt-bot
Copy link
Contributor

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.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants