3 ms·

When you apply "infrastructure as code", you should not be able to change manifests from a mobile phone without using git.

johnjungles 7y ago
Do you mean gitops? I thought infrastructure as code was to make sure your entire cloud environment is code so you can reliability reproduce it. Either way, they’re both concepts to strive for and tools market it this way, but the ideas have been around for a long time. I use kuber for my sandbox clusters to try out new ideas or trouble shoot on the go. I think mobile debugging tools are pretty cool tools. Especially for SRE’s. I used to carry around a foldable keyboard and be able to shell into pods to debug things.
- blackandblue 7y ago
  > sandbox clusters i mean yes. i am of the same sentiment as the original commenter. you don't wanna be messing with production clusters from your mobile phone. getting alerted and monitoring is fine though. i am very curious about all this...
  - johnjungles 7y ago
    Yep this is why I said sandbox clusters. Alerts and monitoring, along with logs is very helpful especially for SRE’s. If you’re on your way to a computer, it helps to get the gears turning
- kissgyorgy 7y ago
  There is no point for production code which is not in Git. As a toy/sandbox, sure this would be handy, but I wouldn't use it for a testing or staging cluster.
  - johnjungles 7y ago
    Why not for testing/staging? Also gitops tools have sync so if you change something it’ll auto generate a commit with its current state. No sure if you know about it but you should check it out! Staging environments don’t want to be too far off from production but at the same time, it can and should be used to test things, so that production deployments are predictable.
ricoberger 7y ago
We are also using GitOps to manage our Kubernetes clusters. I'm using the edit feature for some playground clusters. For production clusters I think the editing of manifests can be forbidden via RBAC which results in an error message for the user, when he tries to use this feature.

johnjungles 7y ago

Do you mean gitops? I thought infrastructure as code was to make sure your entire cloud environment is code so you can reliability reproduce it. Either way, they’re both concepts to strive for and tools market it this way, but the ideas have been around for a long time. I use kuber for my sandbox clusters to try out new ideas or trouble shoot on the go. I think mobile debugging tools are pretty cool tools. Especially for SRE’s. I used to carry around a foldable keyboard and be able to shell into pods to debug things.

blackandblue 7y ago
> sandbox clusters i mean yes. i am of the same sentiment as the original commenter. you don't wanna be messing with production clusters from your mobile phone. getting alerted and monitoring is fine though. i am very curious about all this...
- johnjungles 7y ago
  Yep this is why I said sandbox clusters. Alerts and monitoring, along with logs is very helpful especially for SRE’s. If you’re on your way to a computer, it helps to get the gears turning
kissgyorgy 7y ago
There is no point for production code which is not in Git. As a toy/sandbox, sure this would be handy, but I wouldn't use it for a testing or staging cluster.
- johnjungles 7y ago
  Why not for testing/staging? Also gitops tools have sync so if you change something it’ll auto generate a commit with its current state. No sure if you know about it but you should check it out! Staging environments don’t want to be too far off from production but at the same time, it can and should be used to test things, so that production deployments are predictable.

ricoberger 7y ago

We are also using GitOps to manage our Kubernetes clusters. I'm using the edit feature for some playground clusters. For production clusters I think the editing of manifests can be forbidden via RBAC which results in an error message for the user, when he tries to use this feature.