trastle

We are seeing a similar behaviour while running Version Checker. Would be interested to know if there are recommended values for the limits?

K8s Spire Server: ``` apiVersion: v1 data: server.conf: | server { bind_address = "0.0.0.0" bind_port = "8081" trust_domain = "use.experimental.k8s.ikarem.io" data_dir = "/run/spire/data" log_level = "DEBUG" #AWS requires the use...

K8s Spire Agent ``` ❯ kubectl get configmap spire-agent -n spire -o yaml apiVersion: v1 data: agent.conf: | agent { data_dir = "/run/spire" log_level = "DEBUG" server_address = "spire-server" server_port...

Docker Spire Server: ``` cat /tmp/spire1451413651/server/server.conf server { bind_address = "127.0.0.1" bind_port = "8081" trust_domain = "docker.nsm" data_dir = "/tmp/spire1451413651/data" log_level = "WARN" ca_key_type = "rsa-2048" default_svid_ttl = "1h" ca_subject...

Docker Spire Agent ``` cat /tmp/spire1451413651/agent/agent.conf agent { data_dir = "/tmp/spire1451413651/data" log_level = "WARN" server_address = "127.0.0.1" server_port = "8081" insecure_bootstrap = true trust_domain = "docker.nsm" } plugins { NodeAttestor...

Thanks Denis. New log uploaded here: https://drive.google.com/file/d/1LlW0NyZaoO7q_GY5f5JRnE6LvB0GbxiU/view

I'm not sure I follow the comment about v1.6.1 Do you want me to try downgrading NSM to the older version? I can run the integration test for https://github.com/networkservicemesh/deployments-k8s/tree/release/v1.8.0/examples/k8s_monolith so...

Adding this Stack Overflow ref as it is relevant to the discussion and gives a good description https://stackoverflow.com/questions/50803268/kubernetes-equivalent-of-docker-run-init

What is needed to get this merged in? Seems like it has been good to go for some years.

@cdesiniotis is the roadmap document public? I'd like to keep an eye on the future availability of support for Amazon Linux 2023. Thanks.