Відео

Thanks for another great video! I agree that having a total visibility on all resources is a great pro for this interesting tool, even though personally I'm more a fan of tools doing one thing and doing it well.

Thanks for the video, that's a great solution.

I have followed your steps and it it working fine locally. i can run hello_wasi_http.wasm on my local machine with below command. wasmtime serve /hello_wasi_http.wasm I have configured minikube cluster with wasmtime runtime. for normal helloworld below OCI image is working fine. FROM scratch ADD hello-wasm.wasm / CMD ["/hello-wasm.wasm"] but now i want to build image with http serve. then how can I define docker file with serve? FROM scratch Add the Wasm file to the container ADD hello_wasi_http.wasm /hello_wasi_http.wasm Expose port 8080 EXPOSE 8080 Start the Wasmtime server CMD ["wasmtime", "serve", "/hello_wasi_http.wasm"] i tried this one but not working. can you please tell how can I access http server ?

Hey, awesome video! :) You mentioned showing us some tips and tricks of renovate but I cannot find them anywhere on your channel, can you link them? :)

Viktor just sending a message here from a brazilian devops engineer to thank you so much for your contents.God bless you and your life!You are a good person to provide such a content for free to us, you are helping people on their jobs!Congrats...and please..keep doing your videos!

I don't necessarily prefer declarative languages for state. But I definitely like utilities for building a lot of very similar things at once, the thing that I find weird is that these are all object oriented and not functional. Pure functions are perfect if you're generating a json/yaml output.

Time to rename the channel to PET??

0:21 - Victor is telling us something😂

I was beyond excited when I found out about Steampipe; went all in (mostly using AWS), but it was too unstable for me: gives weird messages about file handles, they do an update and basically change the output structure, plugins start to break all of a sudden, and annoyances here and there caused me to fall back to normal AWS CLI as I was bitten by Steampipe in my workflows. Some of my "all-in" efforts are still in my scripts, and every time I run something, I'm like "wait, did I change back to AWS CLI for this? If not, it's most probably gonna break" So, great tool, but, in my experience, not stable enough

Great video Victor, it shows a really nice overview of how to configure steampipe though I think you left out one key feature about steampipe While it does have a CLI and an installer, you can fully install steampipe into any existing database as an extension giving you the power of your cloud data in your application. If you are building the IDP, then you know exactly how powerful this is. Also, I use postgres for my terraform backend so they are a perfect combination together.

The steampipe is great!! I found it recently for myself

I have been trying steampipe aswell mainly for the "out of box" benchmarks and controls for clouds ands k8s

13:05 Postgres has supported type casting for json for a long time. Cast the jsonb attribute to text and the comparison should work.

Cool tool for service discovery to avoid spending a lot of time querying data from each cloud provider using different API calls.

Viktor, this may not be relevant to this video but wanted to ask this...when using argo cd and crossplane together, which controller does the reconciliation of resources? Is it argo controller or crossplane controller? and how?

Great Vid. Would love to hear more about why Docker was a no go VS nix pkg mgr vs Distrobox

big nix fan

Not get shut in your back? Is this English?

storing the ZSH history in a specified file by using something like: HISTFILE=~/.zsh_history in your .zshrc, fixes that command history problem

Great video! ❤

Excelent tutorial (as always from Viktor). What's missing here is how do I recreate the environments to a new cluster. I did `kubectl apply -k path/to/fleet/apps/fleet-system` (twice because of crd issues) and then `kubectl apply -f path/to/fleet/apps/` and it seems to be working, but I'm not sure if it is "the right way".

I've been eyeballing KEDA to scale to 0 when an environment is not in use-not for production, but for dev, test, and staging environments. I already have a service that does this for non-k8s resources, and I think it would be perfect to add support for k8s resources to my service.

What's the problem, just create 53 sync-waves and forget about it 😝

So would you say that this basically allows serverless computing on kubernetes without all of those extra frameworks like kubeless or knative?

Thank you for the great overview and valuable feedback on Inspektor Gadget. We have made a couple of key updates to our documentation: - Official Helm Charts: Our documentation now includes links to our official Helm charts. - Quick Start Guide: We’ve added a “Getting started -> Quick Start” section. This allows users to try Inspektor Gadget without installation. Thanks again! Your input continues to drive our enhancements, so please keep it coming! ❤

Thanks for another great video! I like the idea behind WASM but there is no drop in replacment or magic formula to make your application run in WASM straightaway. There are changes to make and they may be many depending on the size of your projects. Let's not forget that some WASM implementations for popular languages like Java may not support all the features you need (at least not at the moment). I see security and speed as the 2 major advantages in using WASM but I also know that containers in Kubernetes, when done right and with the help of policies, offer comparable security levels and are isolated too through Linux namespaces. About speed one would ideally need to try its own apps in WASM and containers to tell the difference. All in all switching to WASM would still depends on many things, if your needs justify the effort then maybe it's worth it especially considering tools like Kwasm that could simplify placing your apps in Kubernetes.

Was it by accident that wasmCloud - a CNCF project - missed? It does have a k8s operator, and is architected to stretch across servers and cloud platforms, with or without k8s (thanks to use of NATS as the underlying bus).

Thanks for another great video🎉 I agree with those saying that there's no need to replace or reinvent bash, I just want to add that maybe some people may feel more comfortable with writing Just code than start straightaway the bash journey

I wonder how it would run on RKE2 or K3S. As usual thanks for the great content Viktor!

Hmmmmmmm 🤔

What about the network namespacing and ephemeral storage for the wasm "pod"? is the wasm binary namespaced?

I'm off to play, I'm interested in the start up times, speed of scaling up and down. Thanks for the video !

This is the first video on this subject I've seen that goes into a good amount of detail about the subject matter. Thanks so much clarifying these points. Wanted to ask what the observability story is for Events. If an event is captured by an Eventsource, how do we know that it has been relayed to the Eventbus, and from there that a sensor captures it and successfully invokes a trigger? I guess the pod logs would be of help here but what should we be looking for? Is there a 'friendlier' abstraction or UI that can help here?

Never used a RuntimeClass or WASM yet. Now it makes sense. Thanks Viktor!

The biggest advantage I see is that if you run a wasm runtime instead of a container, you get architecture independence out of the box: if there's a wasm runtime for the arch, your code will run on that arch, without having to think about which archs to support at build time. This is a pain that I'm feeling right now, as I'm setting up my ARM64-based cluster, after coming from an x86-64 based setup. A lot of official packages just don't support ARM.

Hi Viktor, I think you missed one of **THE** major advantages, WASM is platform independent. The Runtime is platform dependent not while building the container image!

Damn I need to check that one out

This is really a missing link for wasm adoption. It would seem that wasm apps are becoming viable. But is it even possible to package large projects as wasm binaries?

Third

Second

first

Thanks for this video. One of the coolest finds in a while. I'm seriously considering replacing devcontainer with devbox for my local development.

Awesome video

Бля я по привьюхе, подумал что это Игорь Гиркин про К6 расказывает)

Victor , I am kind of stuck in the setup section. can I get some help?

# til

IMO it's yet another way to reinvent bash. Bash has all the pros and none of the cons (except for dry-run, which could also be achieved if you mock everything in $PATH) And the bash's syntax flexibility does not mean you MUST use it as an advanced user. You CAN, but you don't HAVE to. And it's perfectly possible to create maintainable bash applications and "makefile" alternatives. IDK, I personally don't see a point in using just/task/makefile. I fail to see what they can offer that bash can't. I mean, you're writing mostly bash in them anyways... So "just" "make" a bash script, write all the "task"s as functions, and call it a day. --list -- `declare -F`. run -- `eval ${1:?Task missing}`. And so on. Why reinvent what's already there...? Why....

besides devtron being all in one.. any others?

i like wiregaurd anything based on wiregaurd is going to be slower due to abstraction.. plus wiregaurd you can self host, while others paywall you and some are difficult to install, alternatively you have zerotier and zrok . if i just need to tunnel my home server to the web then rathole