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
{{ message }}
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
In sync/sync.go, the manifests (files) are compared with the resources in the cluster, by cluster.Exporting and parsing the latter. But export only includes the kinds of resource we "care" about -- hitherto, namespaces, services and deployments. So an annotation on another kind of resource will not be in the results, and not be taken into account.
This is a problem when using the flux.weave.works/ignore annotation on say, a daemonset resource, because the file will be kubectl applyed regardless.
#747 will expand the set of resources we take notice of (to include daemonsets, among others), but ultimately, we want to know about anything that might appear as a manifest.
The text was updated successfully, but these errors were encountered:
The rewrite of the syncing code in #1442 removed this limitation. Sorry for the confusing leftover issue.
(We should still bring the FAQ up to date -- thanks for filing that issue)
In
sync/sync.go
, the manifests (files) are compared with the resources in the cluster, bycluster.Export
ing and parsing the latter. But export only includes the kinds of resource we "care" about -- hitherto, namespaces, services and deployments. So an annotation on another kind of resource will not be in the results, and not be taken into account.This is a problem when using the
flux.weave.works/ignore
annotation on say, a daemonset resource, because the file will bekubectl apply
ed regardless.#747 will expand the set of resources we take notice of (to include daemonsets, among others), but ultimately, we want to know about anything that might appear as a manifest.
The text was updated successfully, but these errors were encountered: