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
In the HelmRelease, I provided values such as the image name and tag but did not specify a security context. I later edited the Deployment manually using the kubectl command to add the security context. However, after reconciling the application, Flux did not recognize the manual change, and the Deployment retained the new security context.
In this case, Flux is only guarding the Git state and not enforcing the desired.
Steps to reproduce
install flux2
Expected behavior
.
Screenshots and recordings
No response
OS / Distro
ubuntu
Flux version
flux: v2.2.3
Flux check
check
Git provider
No response
Container Registry provider
No response
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Describe the bug
In the HelmRelease, I provided values such as the image name and tag but did not specify a security context. I later edited the Deployment manually using the kubectl command to add the security context. However, after reconciling the application, Flux did not recognize the manual change, and the Deployment retained the new security context.
In this case, Flux is only guarding the Git state and not enforcing the desired.
Steps to reproduce
install flux2
Expected behavior
.
Screenshots and recordings
No response
OS / Distro
ubuntu
Flux version
flux: v2.2.3
Flux check
check
Git provider
No response
Container Registry provider
No response
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: