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.		2021-03-29 15:16:18 +02:00
..
faq-migration.md	Move the v1 vs v2 FAQ to the migration section	2021-03-04 10:44:57 +02:00
flux-v1-automation-migration.md	Updated automation migration guide filter tags crd	2021-03-28 21:09:10 +02:00
flux-v1-migration.md	Move the v1 vs v2 FAQ to the migration section	2021-03-04 10:44:57 +02:00
helm-operator-migration.md	fix crd deletion command in v2 migration docs	2021-03-25 18:27:33 +01:00
helmreleases.md	Remove deprecated source behaviour	2021-01-13 11:26:00 +02:00
image-update.md	Update gcr access token in place	2021-03-29 15:16:18 +02:00
installation.md	Improve Azure DevOps install notes	2021-03-18 12:29:07 -06:00
monitoring.md	Add example podMonitor for prometheus	2021-02-24 16:01:00 +00:00
mozilla-sops.md	Fixup a broken reference and a typo in Azure doc	2021-03-21 13:53:27 -04:00
notifications.md	Fix cluster path in examples	2021-01-12 22:15:51 +01:00
sealed-secrets.md	A few minor updates to sealed secrets docs	2021-02-16 21:06:50 +00:00
sortable-image-tags.md	Rewrite to account for numerical sorting	2021-02-12 16:46:30 +01:00
webhook-receivers.md	Rename gotk-system namespace to flux-system	2020-10-29 16:25:16 +01:00