Salvatore Mazzarino

@kzys what is missing to run frecracker-containerd as a replacement of containerd in a kubernetes cluster?

@gnz00 could you point to any resource that claim that the connection remain valid even after the aws session is expired? It's not mentioned anywhere on the aws side. I'm...

About the error I see is the following: ``` {"level":"error","ts":"2022-07-08T18:15:32.681Z","msg":"Operation failed with internal error.","error":"GetMetadata operation failed. Error: pq: PAM authentication failed for user \"temporal\"","metric-scope":55,"logging-call-at":"persistenceMetricClients.go:1424","stacktrace":"go.temporal.io/server/common/log.(*zapLogger).Error\n\t/home/builder/temporal/common/log/zap_logger.go:142\ngo.temporal.io/server/common/persistence.(*metricEmitter).updateErrorMetric\n\t/home/builder/temporal/common/persistence/persistenceMetricClients.go:1424\ngo.temporal.io/server/common/persistence.(*metadataPersistenceClient).GetMetadata\n\t/home/builder/temporal/common/persistence/persistenceMetricClients.go:861\ngo.temporal.io/server/common/namespace.(*registry).refreshNamespaces\n\t/home/builder/temporal/common/namespace/registry.go:422\ngo.temporal.io/server/common/namespace.(*registry).refreshLoop\n\t/home/builder/temporal/common/namespace/registry.go:399\ngo.temporal.io/server/internal/goro.Go.func1\n\t/home/builder/temporal/internal/goro/goro.go:56"} ```

To add more context from official documents https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts-technical-overview.html Here the explanation from aws how the refresh works > The kubelet requests and stores the token on behalf of the pod....

And to add also to the issue, I get the same result even when using an AWS IAM user with acess key id and secret access key.

No. Simply the author reverted the feature in 1.17. This feature can't land implemented in that way for the reasons already explained.

I'm referring here to create automatically a dns entry in the case we have a VIP assigned to a HA control plane.

that’s pretty doable. just start from an example like Tailscale add-on https://github.com/hassio-addons/addon-tailscale you need to bake the nextdns cli on a Docker image and prepare the add-on configuration.

There are many resources out there to start. I’d start from the official add-on template https://github.com/hassio-addons/addon-example. Then create a Dockerfile baking the nextdns cli binary. To move on creating the...

I'm using the image in Home Assistant running on a Raspberry PI 4 and I made the same consideration. However I haven't tried whether a simple change of the base...