🚨 NEWS: Google Cloud Platform da zero: setup account, IAM e prima applicazione
Ecco i punti chiave in breve:
💡 Se hai bisogno di un server per la tua applicazione, ma non vuoi gestire hardware o pagare canoni a vita, Google Cloud Platform (GCP) è una scelta solida. Il problema? Spesso si parte dal deploy...
#iAM #googleCloudPlatform #cloudRun #serviceAccount #billingAlert
Using HTTP/2 Cleartext for a server in Go 1.24
https://www.clarityboss.com/blog/go-http2-cleartext-h2c-cloud-run
I'll give a brief outline of how to enable HTTP/2 cleartext (h2c) in a Go API server when you are using Go 1.24 or newer. This is useful in Cloud Run environments, which handles TLS termination but can take advantage of HTTP/2 features.
Cloud Run の Probe 設計：gRPC 未実装・Distroless・ポートなし Job、それぞれの代替策
https://qiita.com/chinen-gmoconnect/items/4e2c8cc6b4271149f2ea?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Cloud Run meets legacy tech - and the results were complicated. ☁️
I spent last night dockerizing Geneweb 6.08 to run on GCP for @geneee. While I successfully got the service live, the auto-scaling performance and memory handling didn't quite hit the mark, even with Apache in the mix.
It seems this specific legacy version has reached its ceiling. I am pausing here, the search continues.
What is your go-to tech for legacy scaling? 🚀
🔐 How are #GoogleAIStudio deployed apps on #CloudRun protecting the API key so it's not visible in the browser? (although it appeared as if Gemini was called from the client-side...)
➡️ A transparent proxy w/ Service Workers & WebSocket interception prevent key exposure!
【Google Cloud 】Private Service Connect を使ってVPC間の内部通信をする
https://qiita.com/aaaabbbbb/items/604140a1050a71c35aa6?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Cloud Runのアクセス制御を完全理解する（Ingress / IAM / Cloud Armor / IAP）
https://qiita.com/created_on_june_19/items/ed7d16eda2264ba690bb?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
This week I had a bug where my API container was deploying without incident and crashing a second later when /health was checked. The issue was that the crypto provider was not initialized, which caused a panic as soon as /health was checked - it was an ordinary bug.
Because the container started, but then crashed on health check, and it was deployed to #Google #CloudRun, CloudRun kept restarting the container while I was asleep. And crashing it, hitting /health. Then Google's AI must have seen the word "crypto" in the logs because they turned my project off and I woke up to completely broken infrastructure, and an email that said I was CRYPTOMINING in violation of their FREE use agreement.
Now: (a) they charge me for every millisecond of compute time - this is not free use! and (b) crypto means CRYPTOGRAPHY to normal developers. Not freaking crypto currency mining, which I ain't doing.
So now my service is down and I'm waiting for an appeals process - it's been two days.
This was for a personal project but I can't continue to recommend GCP for organizational folks going forward. it is insane to shut down cloud resources on such a thin fact. This is a single 1-CPU CloudRun service that happens to be cycling due to a bug. Stop the API as failing to start properly, and send an email like a NORMAL PERSON. They could absolutely destroy a business this way.
And I think they also need to count false-positive shut downs as part of their uptime calcs. Because ... it is absolutely down time.
Ugh!
Why Serverless VPC Access Exists
https://dhvogel.com/blog/why-serverless-vpc-access-exists.html
Meteora Web
Hacker News
Qiita - 人気の記事
David Schmidt
Guillaume Laforge
Return of Aadmaa
Dan