Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add note to restart image-reflector-controller after AWS IAM role change #508

Merged
merged 1 commit into from
Apr 12, 2024
Merged

Add note to restart image-reflector-controller after AWS IAM role change #508

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/spec/v1beta2/imagerepositories.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -382,6 +382,14 @@ to the IAM role when using IRSA and you have to configure the
`image-reflector-controller` to assume the IAM role. Please see
[documentation](https://docs.aws.amazon.com/eks/latest/userguide/associate-service-account-role.html).

Note when you change the IAM role for the service account, you will need to
restart the `image-reflector-controller` pod to use the new role. This is
always true for any controller running on EKS.

```bash
kubectl rollout restart deployment -n flux-system image-reflector-controller
```

#### Azure

The `azure` provider can be used to authenticate automatically using Workload
Expand Down