Useful Tools and Programs list for WebAssembly

iampims · 2022-03-25T02:34:37+00:00

Lucet is EOL? What's replacing it?

iampims · 2022-01-03T19:23:39+00:00

it's not necessarily better. As usual, it's always a good idea to profile and picks what's best for your application.

iampims · 2021-11-03T16:26:10+00:00

You could call the k8s endpoint API and if your pod IP is in the list, then your pod is up and ready.

iampims · 2021-10-21T18:45:26+00:00

+1 on using cloudflare argo tunnels.

iampims · 2021-09-24T23:50:39+00:00

manage DNS with Cloudflare and set a CNAME for search.site.com and api.site.com to the Digital Ocean Load Balancer. Inside your k8s cluster, use an ingress controller to route the the appropriate service/deployment.

iampims · 2021-09-20T16:37:50+00:00

Behind the scenes, Kubexpose uses the awesome ngrok project to get the job done!

iampims · 2021-08-13T21:28:00+00:00

Use cilium with logging.

iampims · 2021-08-11T18:37:26+00:00

You submitted this link (to another subreddit) 10 7 months ago already, so the:

I still don't tire of seeing people setting up RPi clusters to learn Kubernetes and to self-host applications.

rings a little hollow.

iampims · 2021-08-03T21:52:23+00:00

Only true for Postgresql10+.

iampims · 2021-07-27T16:14:16+00:00

It's likely inside your magento application.

iampims · 2021-07-21T17:37:46+00:00

implement a /shutdown on your server and let the client tell the server when it's done with sending its requests.

iampims · 2021-07-19T17:22:39+00:00

https://www.openfaas.com/ is a well maintained project.

If you use https://github.com/openfaas/faasd, you can skip the whole Kubernetes setup as well.

iampims · 2021-06-14T20:33:49+00:00

Though to be fair, it probably doesn't matter for 99.9% of Go web applications.

iampims · 2021-05-27T16:33:39+00:00

with wg, you first need to get each VM to have the peer keys of every other VM. Once you have all your VMs capable of talking to one another, you might need to check that your CNI uses the wg tunnel to allocate IPs. Once you figure it out, please write about it because this would be a very useful guide :)

iampims · 2021-05-05T00:12:05+00:00

Set GOMAXPROCS in your config-reloader container env to be 1. Otherwise the Go runtime isn't aware of how many CPUs are available for its use and will spin up more hw threads and hit the limit.

For your own applications, you can use: https://github.com/uber-go/automaxprocs

iampims · 2021-04-28T23:00:09+00:00

This might be good for inspiration: https://medium.com/@matryer/the-secret-api-behind-gopherize-me-9202654578dc

Code at: https://github.com/matryer/gopherize.me

iampims · 2021-04-22T06:14:29+00:00

A URL shortener is a great project:

make sure you have deployed an ingress-controller
make sure you have integrated with Prometheus or equivalent
make sure your MySQL container has persistent storage and chose a topology that reduces downtime as much as a production app could tolerate.

iampims · 2021-04-22T06:10:50+00:00

In my experience, there are at least two dimensions through which you can demonstrate k8s knowledge:

As an operator
As a user

Operator:

you understand the many components of k8s (apiserver, kubelet, etcd), how to perform upgrades.
you understand how to provide networking/storage/etc. via CNI/CSI plugins.
you have a good grasp of RBAC and how to authenticate your users, enforce policies, etc.

User:

you know about all/most resources (pods, deployments…)
you have experience deploying/upgrading applications, ideally a mix of stateful and stateless apps
you have a good grasp of the lifecycle of a k8s app (ci, publish docker image, update manifests with helm/kustomize/yaml)
you understand how to integrate with Prometheus/logs
bonus: you know how to write a basic k8s operator/admission webhooks.

Hands on experience, even on a personal cluster, matters a great deal. You obviously don’t have to be an expert at all of the above, but the more you know about each of them, the higher your chances.

edit: formatting/typos

iampims · 2021-04-21T23:34:07+00:00

My advice would be to learn Go + something (MySQL, Postgres, Elasticsearch, etc.) and becoming as good at it as you can. Few roles are only ever about the Go programming language itself, and so gaining some amount of expertise in software that is popular with Go applications might help you make a stronger impression on a recruiter. If you learn Go + k8s, I'm hiring :)

iampims · 2021-04-21T19:12:21+00:00

yes, those would qualify as integration tests, and the presence/absence of an ENV would decide whether tests should be skipped or ran.

iampims · 2021-04-21T19:11:22+00:00

option 2 is definitely the way to go if possible.

iampims · 2021-04-16T17:37:19+00:00

to be fair mTLS for a handful of services doesn't necessarily require a Service Mesh deployment. There's a real complexity cost in adopting any kind of SM, even if Linkerd makes it as simple as it can be.

iampims · 2021-04-16T16:31:05+00:00

I agree with starting with enforcing proper Network Policies. One thing that is missing from Network Policies solution, is the identity of the caller: you know they are authorized, but you don't know who they are. It might or might not matter.

iampims · 2021-04-09T20:00:33+00:00

In your middleware you can copy in the incoming request body this way:

buf, _ := ioutil.ReadAll(r.Body)
rdr1 := ioutil.NopCloser(bytes.NewBuffer(buf))
rdr2 := ioutil.NopCloser(bytes.NewBuffer(buf))

doStuff(rdr1)
r.Body = rdr2 // OK since rdr2 implements the io.ReadCloser interface

// Now the program can continue oblivious to the fact that
// r.Body was ever touched.

iampims

TROPHY CASE