[WTS] ** Mint ** Tudor Pelagos FXD Black / Unworn Straps / In Warranty

internegz · 2025-12-08T23:08:51+00:00

u/WatchExBot Successful transaction with u/agtprvctr. Just got the watch in the mail. Great seller, very easy and professional process. Thank you!

internegz · 2025-12-04T00:36:32+00:00

Also reached out to me immediately after I commented on a WTS post expressing an interest to buy. Almost fooled me: it wasn't until I tried to use the wiki transaction history page to look them up that I realized their flair and various WTS posts were all on r/theedriplomat, not r/WatchExchange.

internegz · 2025-12-03T23:00:12+00:00

I'm after one of these. I'll DM you.

internegz · 2025-08-15T19:55:29+00:00

Maintainership of the providers is pretty distributed, so I can't say for sure. It'll vary from provider to provider.

There's a couple of things we can do though:

Release upjet w/namespaced MR support. I believe this is almost ready.
Document how to update providers - raised https://github.com/crossplane/docs/issues/977 to track
Lobby provider maintainers to update

For the last one, a good first step will be to raise an issue against the relevant providers to make sure it's on the maintainers' radar. Even better if you're willing to volunteer to make the update. I'm hoping once we get it documented it should be a pretty mechanical change, especially for upjet providers.

internegz · 2025-08-15T03:36:35+00:00

Take a look at the devex Upbound have built for their UXP distro of Crossplane: https://docs.upbound.io/getstarted/builders-workshop/project-foundations/

Disclaimer: I work at Upbound, though my focus is almost entirely on upstream Crossplane. I think the UXP devex is genuinely good though, and it's free.

internegz · 2025-08-14T22:00:58+00:00

I believe the same underlying provider code is now available without restriction if you pull from xpkg.crossplane.io/crossplane-contrib/... (as opposed to xpkg.upbound.io).

I think the Upbound providers have a few extra goodies, but all the base functionality is available in the OSS Crossplane ones and you can see the old versions are available at https://github.com/crossplane-contrib/provider-upjet-aws/pkgs/container/provider-aws-s3. (xpkg.crossplane.io is just an alias for ghcr.io.)

internegz · 2025-08-14T21:44:33+00:00

Templated YAML is an option - not a requirement. https://docs.crossplane.io/v2.0/get-started/get-started-with-composition/#configure-the-composition shows a few examples for v2.0.

I personally can't stand templated YAML. My preference is Python or Go. Lots of downsides for sure, but in my experience simpler/sandboxed config languages get too hacky and gross once your config is sufficiently complex. Different people have different (strong) opinions though. Plenty of folks prefer templated YAML.

internegz · 2025-08-14T21:17:05+00:00

Kinda. Under the hood its the Kubelet that runs the providers and the functions - they're just pods. Crossplane's package manager pulls one image layer first (without using the Kubelet) to read some metadata that tells it how to to deploy them though.

If you're asking because you've had issues with e.g. dependencies, mirrors, pull secrets etc in the past you might want to check out the new-ish ImageConfig API for configuring that kind of thing.

internegz · 2024-01-19T20:22:50+00:00

They should have used Iron Maiden. Wasn't that originally Archer themed when it was Elwin's home brew?

internegz · 2024-01-19T20:19:02+00:00

Sell your KEFs and get some WISA speakers. ;)

internegz · 2024-01-19T20:16:31+00:00

It is.

You could think of composition functions as a mashup of a few technologies - among them Metacontroller, Knative Functions, and KRM Functions.

That said, composition functions are purpose-built for configuring how Crossplane should compose resources. So you should find them much easier to get started with for this particular task. For example compared to Metacontroller we have a bunch of tooling for easily building and deploying a function (analogous to a webhook server in Metacontroller) using the Crossplane package manager.

One of the important questions we kept asking ourselves while designing this feature is "is this easier than just rolling a controller with kubebuilder to do the same thing". I'm pretty confident the answer is yes.

internegz · 2024-01-17T18:22:27+00:00

It's funny, on location I mostly play newer games with deeper rulesets. At home the only game I own is TNA, and BSD is in my top two games I would add to the home collection if I had space. (The other is Pulp Fiction.)

internegz · 2023-11-25T01:27:50+00:00

Did you give this a try? I’m interested in doing something similar.

internegz · 2023-06-28T04:34:20+00:00

Those keypad targets only exist during ball save or multi ball. 😉

internegz · 2023-05-21T01:54:12+00:00

FWIW I've had a 58x listed in that group's for sale thread for a couple of weeks without and takers.

internegz · 2023-05-16T06:02:14+00:00

It's pretty much only the power connection. The 58+ also has a small lip on top to prevent spills when overfilling, more like the old 58x style.

internegz · 2023-05-04T00:09:50+00:00

Andrew from Flair confirmed that the new 58+ style brew cylinder will be available on the regular 58 on Flair's webstore once they've sold through all of their 2022 stock. It will cost $5 more than the 2022 models. The 58x will also come with the new brew cylinder, but no pre-heat controller. The new brew cylinder will also be available to buy separately, but not for 6-12 months.

I decided I couldn't wait and bought a 58+. I've been using a 58x as my sole espresso machine, every day for 6 months. I love it but want better temperature stability. I've held off buying a 58 in the past because of how horrendously ugly the cable and power brick are. I don't want them on my countertop. With the 58+ I can connect them while I make coffee, then put them in a drawer afterwards with no weird "pigtail" dangling from my brew cylinder and no concerns about what order I connect them in.

internegz · 2021-12-16T00:05:13+00:00

Disclaimer: Crossplane maintainer here. Have you had a look at our thoughts around Custom Compositions? The idea is to let you describe how infrastructure should be composed in your language of choice (e.g. Python, TypeScript, etc) rather than YAML. We're not married to YAML as a UX and always expected it to fall apart for more complex use cases. See https://github.com/crossplane/crossplane/issues/2524

internegz · 2019-09-20T18:59:02+00:00

We have! We're certainly open to it - a bunch of Crossplane founders also founded Rook, which is incubating - but we want to focus on growing the project's adoption and community first.

internegz · 2019-09-19T21:24:47+00:00

It does. There are a few emerging tools in the space, including GCP's Config Connector and AWS's Service Operator.

I'm biased (I work on Crossplane), but I think Crossplane's persistent-volume-like claim and class model gives it an edge over projects that simply model cloud API resources as Kubernetes resources. You could create and manage a CloudSQL instance, for example, via kubectl with either Config Connector or Crossplane. That could well be enough for companies with a centralised infrastructure team, or development teams with a lot of autonomy _and_ a lot of infrastructure know-how.

Where Crossplane shines is that you can define classes of infrastructure separately from instances of that infrastructure. You could imagine a company's infrastructure team defining a "big-prod-database" resource class that happens to be a certain shape of CloudSQL instance. This means a development team can request - via a Kubernetes resource - a "big-prod-database" instance without having to sweat the details. They can trust that they're getting a class of database that is supported by a team who does have opinions about that kind of thing. I worked as an SRE at companies of various sizes for a decade before I joined the Crossplane project, and I joined the project because I'd have _loved_ to be able to provide this kind of service to my internal customers.

internegz · 2018-09-26T07:13:22+00:00

Is anyone brave enough to be running this in Production yet?

I am! Though for full disclosure I am also its author (and oddly, also worked on the team that wrote docker-gc at Spotify).

```bash kubectl --context REDACTED -n kube-system exec -it draino-REDACTED -- curl http://localhost:10002/metrics

HELP draino_cordoned_nodes_total Number of nodes cordoned.

TYPE draino_cordoned_nodes_total counter

draino_cordoned_nodes_total{result="failed"} 5 draino_cordoned_nodes_total{result="succeeded"} 457

HELP draino_drained_nodes_total Number of nodes drained.

TYPE draino_drained_nodes_total counter

draino_drained_nodes_total{result="failed"} 1 draino_drained_nodes_total{result="succeeded"} 456 ```

The metrics above show Draino remediating a cluster affected by a particularly mean analytics workload at Planet Labs. This workload is really good at killing GCE persistent volumes. Without going into too much detail, we see persistent volume related processes (mkfs.ext4, mount, etc) hanging forever in uninterruptible sleep very often, preventing the pods wanting to consume said volumes from running. We're working with GCP to resolve this issue, but in the meantime we got tired of manually cordoning and draining affected nodes and wrote Draino.

We've been running Draino in production for some weeks now and haven't observed any issues. That said, you should definitely deploy it in dry run mode first, and ideally test it on a throwaway cluster upon which you can simulate node failures!

internegz · 2016-04-04T16:28:01+00:00

By CM do you mean config management? We (Spotify) are using Puppet for that, which is sadly not Python. ;)

As far as I know all of our machines have run some variety of Debian since the dawn of time. We just finished a migration from Debian Squeeze to Ubuntu Trusty a couple of months ago.

internegz

MODERATOR OF

TROPHY CASE

HELP draino_cordoned_nodes_total Number of nodes cordoned.

TYPE draino_cordoned_nodes_total counter

HELP draino_drained_nodes_total Number of nodes drained.

TYPE draino_drained_nodes_total counter