5 ms·

That for sure is not "idealistic devops", but someone missing fixing RBAC to let devs have access to logs of their workload.

• tayo42 3y ago
  Maybe without details or knowing exactly what he means. But I've worked with people that decided you don't get to see any logs on a server except for a select few through some web ui or a log aggregator.
  • eddd-ddde 3y ago
    I know what you are talking about, unfortunately it's way worse than that. The same guy that runs the k8s is the guy that "reviews" my PRs. It's also the same guy that can't get eslint into our PR process, and the same guy that merges code from other people that just out right brick the server because it had some bad syntax. I _wish_ my problems were caused from too strict standards and procedures. But really is just a lack of understanding and cooperation.
  • amtamt 3y ago
    There are production systems handling PII (finance, healthcare etc), where logs are treated as radioactive and only people with trust, training and protective gears should be touching them. This is the case where these are legal/ compliance requirements. Non-prod of those systems can have wide open access to logs, unless someone decides to import prod data for "testing" in non-prod. While I agree access to logs may seem too restrictive, there are some very solid reasons for that... and then we have some cargo-cult and some lack of time/ understanding which causes too restrictive log access where it might not be required.