RT @allafarce: Hertz has sued Accenture for failing to deliver on a $32 million "digital transformation" project.
Follow along as…
2019 campaign summary.
Liberals: don't vote for the other guys, they're scary. Something something tax Labor: here…
RT @SimpsonsQOTD: "Are you wearing a grocery bag?" "I have misplaced my pants."
A frequent pain point in GKE is authentication from a container workload to another service on Google Cloud, such as Cloud SQL. Traditionally, there have been two main ways to do this. First, by over-provisioning permissions—for example, using the node’s built-in service account to authenticate, but this creates unnecessary security risks in the case that the pod is compromised. Second, by creating a new service account identity, and storing its key as a secret and injecting that secret into a pod—a cumbersome solution.
With the upcoming workload identity feature, you can use Google IAM service accounts from Kubernetes pods without having to manage any secrets
RT @GrogsGamut: The climate change debate is trapped in a hell of false balance.
It should not be which party's policy "costs" mor…