debarshri

Please feel free. I do not make any money with this nor there is any hidden intentions here. I am doing this because I am genuinely passionate about PaaS, containers and devops.

I started this when my company as into PaaS. Now we are not, but I still curate and maintain it.

It does not look so bad, does it?

Link has been updated.

It has. I have been maintaining this for past 5 years. It was relevant when I started this project.

Yes

It is backed by github repo, where in creators create a PR. This website is backed by that. This is purely community driven.

I did a quick sanity check before posting. I will do a better housekeeping. I'll remove bad links.

Please note zimki is an honarary mention as it was first paas ever created by canon. Redirect to slideshare is purposely done.

I am not sure if people are using claude design, security review stuff and other tools they have built so far.

Building is the easy part. There are lot of service level stuff that I am sure anthropic will not be able to provide, therefore they are trying to partner with other orgs in that realm.

I am very skeptical about their stuff now.

If you are builder, I believe you should avoid anthropic, it can be default to monopolistic behavior, I am not saying they are doing it, but they could, where in they see what you are building, if you have traction, position a product in that realm. Just saying.

I think itnis ok to use or build vibe coded tools if it is built by experts in the domain and they take the ownership.

Thats might be true.

In enterprise setup when you are dpeloying on customer, airgapped, no access to internet and repositories, you generally dont have control over the infrastructure. It can be as hostile as you can think of.

We are building cloud-native agent harnesses.

This is interesting. We are building something similar too but for remote agents.

It will definitely do that. That we believe you have to make it protocol aware. For eg. if it mysql, it should be proxy that translates as is. then it can't by pass. Also, the proxy should not reveal real credentials.

Interesting times indeed. We are have running protocol aware proxying doing the same including masking for 10+ databases, no tool change required [1]

[1] https://adaptive.live/

Sure, with full disclosure, I don't expect anyone to run in production until I have. Absolutely understand your trust deficit. Just to give you some context, we run our infrastructure in regulated industries like banking, fintech, and public companies.

Once I have embarked on the journey building this from scratch, there are new innovative ideas I can implement not bound to any foundation or org.

Ps. We do not sell it as product it is 100% free and open-source with MIT license.

If you peel off all the layers in Docker Swarm and K8s, technically it has the same level of complexity. In k8s there are a lot of concepts. I would argue you have the same network, storage, and compute complexities as an operator.

Yes, it is external to the cluster.

If you want to do a quick setup, it creates a SQLite DB for the metadata.

I see the installation command is as follows:

curl -fsSL https://simpleobservability.com/install.sh | sudo bash -s -- <SERVER KEY>

I dont feel comfortable running this in prod.

Anything real world tech is hard.

We are hiring, btw.

We do, let me check with my team and post it here.

There were many issues. On top of my mind was, after a DR drill where in a VM was booted, node did not join the cluster. Apart from that bunch of issues due to etcd, longhorn.

Another major one was the CNI stopped work for a particular node. Garbage collection for images was another, we labelled the images, it would still remove then from the node.

Bunch of these kind of issues when our requirement is fairly straightforward. Therefore we are working towards a strip down version.

There is lot of operation complexity in general and most of us can do without.

You can pretty install it without ssh under 60s. The fun starts after it has been installed.

We have been running into lot of issues at production with k3s. There I embarked on journey to writing a kubernetes compliant and equivalent platform in rust with the help of claude [1]. It is a fun little project for now, still figuring out stuff, idea is to keep it minimal and single binary every embedded including CNI, and support various runtimes like docker, containerd etc but also wasm, vms and also jvm.

[1] https://github.com/debarshibasak/superkube

It was always there. k9s for instance, it started getting noticed recently. With coding agents, it is even easier to build.

I agree with operational complexity of kubernetes. That is the reason why we started writing single binary rust based kubernetes compliant platform [1]. Think of it like a minimal kubernetes rewritten in rust. Basically, you can deploy with kubectl.

I like wasm idea here. I'm probably going to add wasm as runtime for this project.

[1] https://github.com/debarshibasak/superkube

Anthropic should release mythos to general public.

Someones shit is someones money, yo!

We have been running LLM and coding agents for a while now and my overall observation is that it is a powertool or a crane, it is not a decision making tool.

Now in my org, people who have great understanding of concepts, deeper engineering understand have exponential productivity. People who dont or new in the workforce, juniors, are generating hell-ish code without understand as long as it runs they think the job is done. And this is where the problem is.

The llm creates an intellectual gap within the org and it just widens it as more and more it gets used. You might end up not trusting stuff within the org if code is generated by later.

you can have dedicated deployment per customer per case, segregating it logically. I have seen this happen in larger law firms. It could be based on groups, teams, partners etc.

As we speak, there is github api issues going on.

It is an enterprise product. Enterprise products are not cheap. Also, you should have certain scale to buy an enterprise platform. By setting certain price, they expect you as a business to have scale as there are support and service level agreements the org wants to adhere to, it is also an investment from the org side.

It is pretty common playbook.

Funny enough, GitLab, has a dutch founder.

I am building in cybersec space. I dont think you even need script kiddies now. Internal employees run dangerous bad ops with AI that itself is a cybersec nightmare.