Svyatoslav

@damian-aifinyo Just faced the same issue and this config section helped to update these envs: ``` global: #### storage: type: "S3" bucket: activityPayload: log: state: workloadOutput: ```

Faced the same issue and seems it was fixed in https://github.com/aws/containers-roadmap/issues/1262 I've tried with `AmazonEC2ContainerRegistryReadOnly` policy attached to EKS node and from node itself we can list tags with token,...

Hey @davidcollom thanks for the update! I've checked today on one of my clusters and upgrade from `0.5.3` > `0.6.0`, but unfortunately still the same issue with Public ECR gallery...

@brian-brazil @roidelapluie Thanks for the feedback, as I could see [#7086 ](https://github.com/prometheus/prometheus/pull/7086)is related to IPv6 label only, does it mean that we need to add additional API call ?

Sorry I didn't get it completely, but what if EC2 has no any IPv6 assigned ? And has only multiple Private IPv4 addresses.

> Looks like you are not setting a block page, you may completely omit that settings block. we have added "" to valid values of mode to avoid this issue...

@jhutchings1 @rexscaria Thanks for the updated. I tested it on provider version 5.12.0 and resources is still in permanent change during each apply: ``` # cloudflare_zero_trust_gateway_settings.general will be updated in-place...

@rexscaria I tried to change/check settings and re-apply, then tried to remove resource and create it again in terraform, but the same situation. I collected the terraform debug logs if...

@rexscaria I can confirm that minimal settings have no drift. After plan/apply no drift detected: ``` # cloudflare_zero_trust_gateway_settings.general will be updated in-place ~ resource "cloudflare_zero_trust_gateway_settings" "general" { ~ created_at =...