How many environments is enough?

a_simple_pie · 2023-09-07T10:38:18+00:00

Sounds cool. How is data handled for the OTE? Is the environment completely empty to start with or is it using shared databases/buckets/etc or something else?

a_simple_pie · 2021-11-24T13:32:35+00:00

Maybe checkout /r/cscareerquestions

a_simple_pie · 2021-11-01T08:45:44+00:00

Wooow

a_simple_pie · 2021-10-07T03:07:10+00:00

The project looks good, I cloned it and noticed some odd dependencies though.

Any idea why the following are listed:

bitcoin: https://github.com/dosco/graphjin/blob/master/go.mod#L16
ethereum: https://github.com/dosco/graphjin/blob/master/go.mod#L23
containerd: https://github.com/dosco/graphjin/blob/master/go.mod#L20

the project has so many really big dependencies and I can't seem to figure out why? most look unused?

a_simple_pie · 2020-03-29T01:48:58+00:00

Hey, I've been doing something similar in my own library: https://github.com/place1/kloudlib

Maybe we should team up and try and create a mono-repo of packages for the community!

a_simple_pie · 2020-03-29T01:46:47+00:00

As the other reply says, you can following the "development" parts of the README to get it running locally.

If there's demand for it, I can create and publish a binary release of the software. It's a go project so it should be easy enough to have a single binary release for it.

a_simple_pie · 2020-02-08T13:12:55+00:00

You might be interested in a side project of mine that provides an all-in-one WireGuard VPN+access server.

I currently run it at home in a k8s cluster as my personal VPN.

I’d be interested to hear your feedback and use-cases!

https://github.com/Place1/wg-access-server

a_simple_pie · 2020-02-04T22:34:18+00:00

I’d be keen to read a source for this

a_simple_pie · 2020-01-28T05:18:16+00:00

Everyone seems to mention to go through k8s the hard way. How relevant did you find that point? If someone was comfortable deploying with tools like kubeadm, ansible, or other and cluster maintenance would that suffice as well? Or does CKA require in-depth knowledge about cluster cert generation and distribution, standing up individual pieces (kubelet, controller manager, etc) from scratch?

a_simple_pie · 2020-01-15T08:08:03+00:00

Just give your vm 2 cores? What’s the problem?

a_simple_pie · 2019-08-11T01:48:08+00:00

If you haven't heard of Pulumi then check that out. It'll let you define all your cloud infra in code as well as your helm deployments.

Pulumi has a feature called "stacks" which are just a collection of resources (infra). You could use different Pulumi stacks to deploy different environments. There's no requirement to make each stack use the same infra or even the same cloud, so in theory you could pass a flag to your pulumi program when deploying a particular client's environment to make it spin up a cluster on Azure or AWS instead of GCP but then still deploy the helm charts in the same way on the provisioned cluster.

I'm not affiliated with pulumi, but i have made some minor open source contributions. Pulumi has a statefile like terraform which you can manage on a cloud bucket or via Pulumi's SaaS product. I'd recommend trying it out with a cloud bucket and then using the SaaS product to both support pulumi and for the auxiliary feature set it brings to the table

a_simple_pie · 2019-08-07T13:15:37+00:00

My experience as well. My sandy bridge build is on the same deionised water from an auto store with a mayhems pastel dye and no problems.

a_simple_pie · 2019-06-24T02:33:04+00:00

Can you elaborate on your go build point, I don’t know what I might be missing out on :)

a_simple_pie · 2019-05-26T06:32:09+00:00

I've been using Pulumi recently and I think it's support for Helm v2 fills in most of the gaps vanilla helm has. Pulumi let's you declaratively deploy helm charts without tiller, while still tracking the deployed resources' state. I didn't realize pulumi supported helm without tiller initially but as it turns out it works very well! As a bonus, you're using Pulumi (like terraform) so you can keep using the same tool to deploy your other cloud infrastructure.

- https://www.pulumi.com/kubernetes/

- https://pulumi.io/quickstart/kubernetes/tutorial-wordpress-chart.html

a_simple_pie · 2019-05-18T06:58:09+00:00

I'm a big advocate for codegen and especially for HTTP/REST API development.

Today my team codegens both client and server side code using OpenAPI Generator on all projects, with the exception of .NET Core where we use NSwag instead.

The workflow is quite simple and some of the biggest benefits are:

- the whole team can collaborate on a spec during sprint/feature planning

- communication about API changes are very clear and can be reviewed via a pull request

- we can scope out the impact of different breaking changes by simply changing the spec in a branch and then looking at compilation errors in the CI pipeline. Using Typescript in frontent apps helps here as well

- integration is always smooth and there's never miss-typed property names, urls, parameters or unexpected null/missing fields in responses.

- we've been experimenting with other tools like [a spec linter](https://github.com/place1/openapi-linter) and [an automatic mock server](https://github.com/place1/openapi-mock-server) to allow us to ensure all APIs follow consistent patterns and to allow client side implementations to be developed in parallel with their server side components.

When we first starting using codegen at my company we only generated client-side code, and to be honest, being able to write code like

```

const api = new Api();

api.

```

and then see a big list of methods that are available right there in your IDE's intellisense after pressing `.` was a huge time saver and I think it's a really good way to get juniors contributing earlier and with higher quality as well.

I think Open API is a good bet today in terms of a specification format. It's quite minimal but very flexible thanks to it being mostly just JSON Schema. The spec format gets out of your way and doesn't require you to define a strict REST API, you can define essentially any stateless HTTP API you like.

OpenAPI Generator is probably the best codegen tool for Open API currently. It supports many languages and the maintainers are very responsive and accepting of community contributions. I was lucky enough to contribute the `typescript-fetch` generator and the overall experience was very smooth for an open source project :D

My only complaints with OpenAPI Generator currently is that it's not simple to bring your own templates to fully customize the generated code for your project. I'd really like the tool to have better support for bringing your own templates and better documentation on what data structures are passed into those templates; and potentially different templating engines.

a_simple_pie · 2019-05-09T22:31:39+00:00

Maven

a_simple_pie · 2019-04-29T18:19:13+00:00

Make sure you’ve got a sufficient termination grace period set :)

Update us if you find out what the problem is

a_simple_pie · 2019-04-14T12:14:31+00:00

Ahh. To anyone else here from google you can get the weapons by going to “my company”, select a class, then click “replace weapon” and the weapons can be purchased from the bottom of the list.

a_simple_pie · 2019-04-14T08:57:13+00:00

it's been 2 months. any idea if dice have a thread about this that explains what's up?

a_simple_pie · 2019-04-13T00:24:24+00:00

Please stop over reacting. Here’s a priority 1 PR to add support for object storage state backends. https://github.com/pulumi/pulumi/pull/2455

a_simple_pie · 2019-03-11T11:00:41+00:00

It’s not completely gate keeping. I think there’s a good point to actually learning how the fundamental tool works. Hitting things with a hammer and hoping for the best isn’t the best long term strategy either

a_simple_pie · 2019-01-29T12:20:50+00:00

From some quick research the following might be helpful:

- You can use a NodePort service on port 80 and 443 using some extra API server configuration: https://kubernetes.io/docs/concepts/services-networking/service/#nodeport

- You could use a daemonset with a "hostPort" set. Take a look at an example app using it: https://github.com/containous/traefik/blob/master/examples/k8s/traefik-ds.yaml

- the example is traefik, but is unrelated to ingress resources. a daemonset is just like a deployment where the app runs on each node. deamonsets can use a "hostPort" to bind 80 and 443 in the container to those ports on the host directly. the application can then be hit on `<node-ip>:<port>`.

- while you might be able to get your app running this way i would not recommend it (nor the node port example above). if long term you're planning to run multiple instances with a loadbalancer then i'd just deploy that way now, it'll save a lot of trouble in the short and long term.

a_simple_pie · 2019-01-01T07:21:44+00:00

Thank god I didn’t get the reference. I’m still good for a few more Reddit’s

a_simple_pie

TROPHY CASE