Very valid reasons Raphael! Do you think we could add freedom to inject infra-level chaos (disk, node, network - typical experiments with blast radius enough to "impact" other dev groups on different namespaces) to that list, considering chaos is increasingly appearing in a dev's checklist today as much it continues to be an SRE pursuit?
Thank you Raphael. It appears that teams or individuals manage themselves within a namespace while they are small or during early dev stages.. mostly stateless applications.
A Freelance DevOps doing container stuff and automating unhealthy amounts of software.
Need something automated or containerized? Feel free to hit me up :)
I am inclined to agree. For small teams it probably has no instantly apparent value as compared to having/building more features.
I haven't seen much chaos engineering done as of yet, but I do think it can be a vital component in SRE and training.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Very valid reasons Raphael! Do you think we could add
freedom to inject infra-level chaos(disk, node, network - typical experiments with blast radius enough to "impact" other dev groups on different namespaces) to that list, considering chaos is increasingly appearing in a dev's checklist today as much it continues to be an SRE pursuit?Thank you Raphael. It appears that teams or individuals manage themselves within a namespace while they are small or during early dev stages.. mostly stateless applications.
I am inclined to agree. For small teams it probably has no instantly apparent value as compared to having/building more features.
I haven't seen much chaos engineering done as of yet, but I do think it can be a vital component in SRE and training.