3 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
In the end, this is what worked for us to migrate from a ConfigMap authentication mode to API only without downtime
With a long delay (days) between each task:
- update the cluster from CONFIG_MAP to API_AND_CONFIG_MAP (this will create access entries for Fargate and managed node groups), do not touch the ConfigMap content
- create our own access entries for accounts needing them, still without updating the ConfigMap content
- switch the cluster to API only
- delete the aws-auth ConfigMap, as it is no longer needed
répondu il y a un mois
1
This is not a good answer, but it appears that by deleting and re-recreating the Fargate profiles, everything starts working again
répondu il y a 2 mois
0
I can confirm the same behavior after recently migrating to access entries. I can also confirm the "workaround" of deleting the fargate profiles and recreating them works to resolve it but it is not ideal and may not be possible for all workloads.
Still, thanks to @NIGo for that nudge.
répondu il y a 2 mois
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an