You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We ran into this problem today. One of our app failed to get credstash credentials from DynamoDB. There has been some updates to the k8s cluster where these apps were running, so the app team called up DevOps to troubleshoot. It turned out that the app was updated and credstash updated somehow which broke it.
The point here is that, they suspected the infrastructure/k8s cluster was at fault first before their app. This shows that they have less confidence in the infrastructure upgrades than they do in their own app upgrades.
There should be a test like the "statefulset" test where a pod is launched which uses some IAM or GCP scope role to perform an action. Then at least this path would be some what tested. At first we were unsure if it was b/c of the k8s cluster updates. It shouldnt be since we didn't touch any of that stuff but who really knows.
The idea here is that to perform some test to give us and the app team confidence on what is tested during every cluster update change.
The text was updated successfully, but these errors were encountered:
We ran into this problem today. One of our app failed to get credstash credentials from DynamoDB. There has been some updates to the k8s cluster where these apps were running, so the app team called up DevOps to troubleshoot. It turned out that the app was updated and credstash updated somehow which broke it.
The point here is that, they suspected the infrastructure/k8s cluster was at fault first before their app. This shows that they have less confidence in the infrastructure upgrades than they do in their own app upgrades.
There should be a test like the "statefulset" test where a pod is launched which uses some IAM or GCP scope role to perform an action. Then at least this path would be some what tested. At first we were unsure if it was b/c of the k8s cluster updates. It shouldnt be since we didn't touch any of that stuff but who really knows.
The idea here is that to perform some test to give us and the app team confidence on what is tested during every cluster update change.
The text was updated successfully, but these errors were encountered: