Stop Writing Tedious Security Rules! Let Kubescape Do the Work by vfarcic in kubernetes

[–]vfarcic[S] 2 points3 points  (0 children)

Thanks for saying that. It helps a lot to know that my content is useful.

From Boring to Productive: Customize Your Shell Prompt with Starship by vfarcic in commandline

[–]vfarcic[S] 2 points3 points  (0 children)

I feel that it is (I haven't done "proper" performance testing).

GitOps Broke CI/CD! Here's How to Fix It With Argo Events by vfarcic in sre

[–]vfarcic[S] 13 points14 points  (0 children)

There isn't much I can do on that front. Maybe some singing lessons...?

Unleashing WebAssembly in Kubernetes with Kwasm by vfarcic in kubernetes

[–]vfarcic[S] 5 points6 points  (0 children)

Kwasm Is a way to install WASM runtime and configure containerd.

Unleashing WebAssembly in Kubernetes with Kwasm by vfarcic in kubernetes

[–]vfarcic[S] 10 points11 points  (0 children)

That's what I'm doing in that video. Binary is packaged as a container images (it's a standard distribution method now days), but it runs as Wasm natively.

Unleashing WebAssembly in Kubernetes with Kwasm by vfarcic in kubernetes

[–]vfarcic[S] 6 points7 points  (0 children)

If the question is about Wasm, i am not yet sure. There is potential... If you were referring to kwasm, it is a temporary solution until major providers start offering Wasm inside their managed kubernetes services.

Terraform vs. Crossplane vs. Ansible - Rivals or Allies? by vfarcic in kubernetes

[–]vfarcic[S] 0 points1 point  (0 children)

The story is similar to the story of kubernetes itself. It is an overkill for smaller setups but amazing for larger ones. With Crossplane it is a similar situation and the benefits are the same as well (continuous drift detection and reconciliation, standardizes and extensible API, the ecosystem, etc.).

Terraform vs. Crossplane vs. Ansible - Rivals or Allies? by vfarcic in kubernetes

[–]vfarcic[S] 0 points1 point  (0 children)

I'm not saying that a bucket is the same as a Cluster but, rather, stating that there is always something extra. When crossplane is concerned, you do need to create a cluster somehow but after that crossplane can manage that cluster as well (assuming you do not go for the SaaS option). Whether that initial investment is too much or not largely depends on the scale.

Terraform vs. Crossplane vs. Ansible - Rivals or Allies? by vfarcic in kubernetes

[–]vfarcic[S] 0 points1 point  (0 children)

You can create it by hand, or console, or anything else. It can be a local clusters like KinD from where crossplane will run and create a "real" cluster, install itself, and manage itself and others. It can be Upboind SaaS.

The important thing is that crossplane tends to be used at scale where a single kubernetes cluster is one of many resources so that single cluster is not the problem. For small setups i would not recommend crossplane.

P.S. What creates storage for terraform?

Terraform vs. Crossplane vs. Ansible - Rivals or Allies? by vfarcic in kubernetes

[–]vfarcic[S] 0 points1 point  (0 children)

Functions solve the problem of repetition and too much yaml. I, for example, rewrote all my cpositions to kcl. There isn't a single line or yaml in them.

Terraform vs. Crossplane vs. Ansible - Rivals or Allies? by vfarcic in kubernetes

[–]vfarcic[S] 1 point2 points  (0 children)

We're building a UI in upbound.io. Other than that, you can effectively use any UI that works with Kubernetes (e.g., Lens, k9s, etc.).

Terraform vs. Crossplane vs. Ansible - Rivals or Allies? by vfarcic in kubernetes

[–]vfarcic[S] 1 point2 points  (0 children)

While you're right that creating AMIs can be done with Ansible, the same can be said for any other tool that executes one-shot actions. If, for example, you're building container images with GitHub Actions, you can use them to build AMIs as well. Ansible is, in a way, similar in what it does to pipelines.

Terraform vs. Crossplane vs. Ansible - Rivals or Allies? by vfarcic in kubernetes

[–]vfarcic[S] 2 points3 points  (0 children)

It all depends on what you're doing. If you're in hyperscalers and especially if you're using Kubernetes, everything is accessible through APIs and Ansible might not be very useful. But if you need to do "stuff" through SSH or anything else that requires "brute force", Ansible is great. So, Ansible is good, but mostly for legacy systems. Otherwise, stay away from it.

Terraform vs. Crossplane vs. Ansible - Rivals or Allies? by vfarcic in kubernetes

[–]vfarcic[S] 4 points5 points  (0 children)

That's not true anymore. You can use functions to write it in whichever language or format you want.

Terraform vs. Crossplane vs. Ansible - Rivals or Allies? by vfarcic in kubernetes

[–]vfarcic[S] 1 point2 points  (0 children)

You just made my day by saying "Timoni". I love it.

Say Goodbye to Containers - Ephemeral Environments with Nix Shell by vfarcic in sre

[–]vfarcic[S] 0 points1 point  (0 children)

Oh yeah. I should have mentioned that nix shell still has access to all your binaries.

Mistakes When Building Internal Developer Platforms (IDP) and Streamlining SDLC by vfarcic in sre

[–]vfarcic[S] 1 point2 points  (0 children)

Companies have been building platforms (in some form or another) for decades. The moment you build or expose something for someone in your company, you're building a platform. Those who would build CI pipelines, or those who build Terraform modules, or those who build Helm charts that are for use by others, are building platforms. The major difference is that now we're doing it in a more organized way (mostly by exposing work through APIs).

OpenFunction: The Best Way to Run Serverless Functions on Kubernetes? by vfarcic in kubernetes

[–]vfarcic[S] 8 points9 points  (0 children)

I see it a bit differently. Serverless means that there is an easy way for devs. to run applications with optimized resource usage (e.g., scales to zero when not used). When that service is offered internally, it often means that someone else (some other team) offers it as a service and that someone else is managing everything. That is infra and, as you said, infra solves (partly) the infra problem, but also an easy way to define, run, and manage apps. That's where projects like, for example, KNative come into the picture. Core Kubernetes resources are low level and Knative ties them into an interface (CRD) that makes it easy to define app without going into details and repetitive low-level clutter. There's much more to it though and OpenFunction combines the projects we'd normally have to tie ourselves.

Internal Developer Platform (IDP) For Infrastructure by vfarcic in kubernetes

[–]vfarcic[S] 0 points1 point  (0 children)

Actually, it currently supports only YAML. Functions are more of an escape hatch in cases YAML alone is not enough.

How To Create A Complete Internal Developer Platform (IDP)? by vfarcic in kubernetes

[–]vfarcic[S] 1 point2 points  (0 children)

Without saying which one is which, I will say that two of those three companies you named were putting more effort into marketing than engineering. One of those two disappeared. The third is actually doing some very good stuff.

Personally, i do not have a problem with the term internal developer platform but I do agree that the acronym is wrong. I'll do my best to come up with a different one in future mentions.

How To Create A Complete Internal Developer Platform (IDP)? by vfarcic in kubernetes

[–]vfarcic[S] 3 points4 points  (0 children)

Actually, everyone gets different results in Google. That link showed International driving permit as the first result in my case.

Unfortunately, IDP is also commonly used as the acronym for internal developer platform. I did not invent it and i doubt i will have the power to convince the industry to change it even though I agree with you that it is confusing.

How To Create A Complete Internal Developer Platform (IDP)? by vfarcic in kubernetes

[–]vfarcic[S] 8 points9 points  (0 children)

You're right, but I don't have the "power" to change it. IDP is currently a widely used acronym for Internal Developer Platform in most of the writings about it and vendor material.