You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Mieszko Wawrzyniak a99e98ea55 Update gcr access token in place ... It's possible to update secrets in place instead of removing and creating a new one. But what's wrong with the old way of doing things you may ask. If jobs for GCR synchronization and token refreshment lunch at the same time and they sometimes will we will get the following error: `Secret "gcr-credentials" not found` This happens because: 1. token was deleted by Token Refresh Job 2. GCR synchronization will begin and fail because there is no token 3. new token will be created. Updating the token in place fixes this issue.		4 years ago
..
faq-migration.md	Move the v1 vs v2 FAQ to the migration section	4 years ago
flux-v1-automation-migration.md	Updated automation migration guide filter tags crd	4 years ago
flux-v1-migration.md	Move the v1 vs v2 FAQ to the migration section	4 years ago
helm-operator-migration.md	fix crd deletion command in v2 migration docs	4 years ago
helmreleases.md	Remove deprecated source behaviour	4 years ago
image-update.md	Update gcr access token in place	4 years ago
installation.md	Improve Azure DevOps install notes	4 years ago
monitoring.md	Add example podMonitor for prometheus	4 years ago
mozilla-sops.md	Fixup a broken reference and a typo in Azure doc	4 years ago
notifications.md	Fix cluster path in examples	4 years ago
sealed-secrets.md	A few minor updates to sealed secrets docs	4 years ago
sortable-image-tags.md	Rewrite to account for numerical sorting	4 years ago
webhook-receivers.md	Rename `gotk-system` namespace to `flux-system`	5 years ago