Talos Linux
talos.dev
Talos Linux
1–10 of 45 posts
Re: Talos Linux
#2Re: Talos Linux
#3> Talos runs in memory from a SquashFS, and persists nothing, leaving the primary disk entirely to Kubernetes.
Hmm so if the entire disk is unused where is /boot in this configuration?
Re: Talos Linux
#4> Ephemeral > Talos runs in memory from a SquashFS, and persists nothing, leaving the primary disk entirely to Kubernetes. Hmm so if the entire disk is unused where is /boot in this configuration?
Re: Talos Linux
#5Re: Talos Linux
#6So, no actual threat modelling, third party audits or integration and unit testing is done? Yes, that appears so.
Re: Talos Linux
#7Can anybody help explain when organizations should use Talos instead of cloud-vendor-managed Kubernetes offerings (EKS/AKS/GKE)? Especially considering that the managed offerings now fit most regulatory requirements (e.g. EKS is FedRAMP-High Authorized)? Or does Talos see most of its use in on-prem environments?
1. Learning. I want to self host to learn the stack top to bottom.
2. Build your own service.
3. Why not? (probably the best, most hackerish option)
> Especially considering that the managed offerings now fit most regulatory requirements (e.g. EKS is FedRAMP-High Authorized)?
Standards that meet regulatory requirements may not be updated or secure enough to meet private sector needs.
Re: Talos Linux
#8Re: Talos Linux
#9> Security: Talos reduces your attack surface: It's minimal, hardened and immutable. All API access is secured with mutual TLS (mTLS) authentication. So, no actual threat modelling, third party audits or integration and unit testing is done? Yes, that appears so.
Re: Talos Linux
#10> Security: Talos reduces your attack surface: It's minimal, hardened and immutable. All API access is secured with mutual TLS (mTLS) authentication. So, no actual threat modelling, third party audits or integration and unit testing is done? Yes, that appears so.
Did you just read a marketing blurb on their landing page and decide after 5 seconds they don't do unit testing? I guess we can also assume they don't brush their teeth every morning because they didn't mention that either.
https://www.talos.dev/v1.0/learn-more/philosophy/ "Security" section makes no mention of independent audits. It just boldly claims "There are no passwords in Talos" as if that was a panacea for security.
The existing integration tests don't verify any assumptions about security, only that the configuration is valid. Please correct me if I'm wrong or missed anything.
If you're going to call something "secure" you need to prove it.