-
Notifications
You must be signed in to change notification settings - Fork 160
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
Metallb installation with driftDetection: mode: enabled
failed to apply revision
#855
Comments
driftDetection: mode: enabled
failed to apply kustomise revisiondriftDetection: mode: enabled
failed to apply revision
Can you please share the The precise fields can be observable from the controllers logs, they should be logged as |
Please see the .status of the HR
Trying to set the controller log to debug. |
How can I extract this |
It should be logged right after "detected changes in cluster state", see: Without knowing the specific path, you should at least be able to confirm the issue is indeed due to detected drift by excluding the resource in full. |
This is what I found in my logs.
IIRC, I need to ignore both CRDs For some reasons these are changed after Helm installs it, right. |
We are experiencing this problem as well. We see status:
conditions:
- lastTransitionTime: "2024-01-12T11:10:18Z"
message: dependency 'monitoring/xx' is not ready
observedGeneration: 17
reason: ProgressingWithRetry
status: "True"
type: Reconciling
- lastTransitionTime: "2024-01-11T10:06:53Z"
message: dependency 'monitoring/xx' is not ready
observedGeneration: 3
reason: DependencyNotReady
status: "False"
type: Ready
- lastTransitionTime: "2024-01-09T16:54:05Z"
message: Helm install succeeded for release metallb/metallb.v1 with chart metallb@0.13.12
observedGeneration: 1
reason: InstallSucceeded
status: "True" But in the helm-controller logs we see {"level":"info","ts":"2024-01-12T11:03:47.753Z","msg":"checking 1 dependencies","controller":"helmrelease","controllerGroup":"helm.toolkit.fluxcd.io","controllerKind":"HelmRelease","HelmRelease":{"name":"metallb","namespace":"metallb"},"namespace":"metallb","name":"metallb","reconcileID":"d7751623-4737-417b-82cc-d1db35fdbfe7"}
{"level":"info","ts":"2024-01-12T11:03:47.753Z","msg":"all dependencies are ready","controller":"helmrelease","controllerGroup":"helm.toolkit.fluxcd.io","controllerKind":"HelmRelease","HelmRelease":{"name":"metallb","namespace":"metallb"},"namespace":"metallb","name":"metallb","reconcileID":"d7751623-4737-417b-82cc-d1db35fdbfe7"}
{"level":"info","ts":"2024-01-12T11:03:48.117Z","msg":"detected changes in cluster state: removed: 0, changed: 2, excluded: 0","controller":"helmrelease","controllerGroup":"helm.toolkit.fluxcd.io","controllerKind":"HelmRelease","HelmRelease":{"name":"metallb","namespace":"metallb"},"namespace":"metallb","name":"metallb","reconcileID":"d7751623-4737-417b-82cc-d1db35fdbfe7"}
{"level":"info","ts":"2024-01-12T11:03:48.163Z","msg":"running 'correct cluster drift' action with timeout of 5m0s","controller":"helmrelease","controllerGroup":"helm.toolkit.fluxcd.io","controllerKind":"HelmRelease","HelmRelease":{"name":"metallb","namespace":"metallb"},"namespace":"metallb","name":"metallb","reconcileID":"d7751623-4737-417b-82cc-d1db35fdbfe7"}
{"level":"info","ts":"2024-01-12T11:03:48.584Z","msg":"detected changes in cluster state: removed: 0, changed: 2, excluded: 0","controller":"helmrelease","controllerGroup":"helm.toolkit.fluxcd.io","controllerKind":"HelmRelease","HelmRelease":{"name":"metallb","namespace":"metallb"},"namespace":"metallb","name":"metallb","reconcileID":"d7751623-4737-417b-82cc-d1db35fdbfe7"} --> |
Setting the log-level to debug showed us the path for the (automatically) changed data. driftDetection:
ignore:
- paths:
- /spec/conversion/webhook/clientConfig/caBundle
target:
kind: CustomResourceDefinition Still I think the status message has to be fixed...because it seems to not change, if the HelmRelease goes into "ProgressingWithRetry" - it just keeps the status message from before, is my guess (without looking into the code). |
See also: metallb/metallb#1681 |
I'm trying to setup Metallb with this Kustomization:
And this Helm Release:
flux version
flux get kustomizations
is showing it is never Ready and marked as Unkown.In the logs of the helm-controller I have
k -n flux-system logs helm-controller-<id>
The application is successfully installed, the pods are Ready, the HelmRelease is marked as Ready.
However, the Kustomization never finish.
It continuously try to reconcile the HelmRelease for some reasons.
I tried many times to manually reconcile, tried with --with-source.
I tried to remove the HealthCheck and set it to
wait: true
, nothing is working.The only way to make it work is to remove every HealthCheck or wait:true statement and it is then successfully deployed.
The text was updated successfully, but these errors were encountered: