basil404.bsky.social
Cloud architect. I like containers, openstack, terraform, ansible, and black espresso.
I am not speaking officially on behalf of my employer, everything I say is as a private individual.
443 posts
131 followers
247 following
Active Commenter
comment in response to
post
You’ll note they were careful to say that it’s still the place for your pipelines :)
comment in response to
post
If you want that, can you not just use virtual machines?
comment in response to
post
The nice thing about that scale is that there’s no real reason not to follow your heart :-) you don’t need to be as brutally efficient in your architecture
comment in response to
post
Kubernetes serves a very specific purpose. It provides the ability to host cloud native applications without needing the higher order paas and saas services of a public cloud vendor. it’s only really valuable at scale.
comment in response to
post
There is no mention in that article about what they’ve done at CERN to manage the data from the particle accelerator. I would imagine there to be something parallels.
comment in response to
post
Pretty good song though!
comment in response to
post
My take on language models in coding is that it takes whatever you have and multiplies it. If you start with zero, you still have zero, but if you get some of the basics, you can do way more than without it.
comment in response to
post
I don’t know what it is with CI tools - it was the same with Jenkins. I would typically replay a Jenkins run with edits. We can’t even do that in Actions.
comment in response to
post
One of the most useful things a finops team can do is provide visibility and waste detection tools.
comment in response to
post
It should be possible to declare requirements and not need to support what provides them. So for example, he can require that there be a persistent file system with a specific name mounted, and make it up to the client to decide how to do that.
comment in response to
post
The line between application and deployment can be blurry. Ideally, he would provide a container image and some requirements. It would be up to the clients to meet them. For example, he could require an SSL certificate and specify how the container expects the secret to be configured.
comment in response to
post
At the end of the day, the people writing code and the people ensuring it runs are working toward the same goal. Developers should care how their code is running, for the same reasons infrastructure people care what the code is doing. Decisions made on one side have impacts on the other.
comment in response to
post
The thing is this completely new domain was created to bridge the gap between running code and writing it. These two things are intrinsically linked. Trying to do either without considering the other will result in worse outcomes.
comment in response to
post
Application developers can’t be insulated too much from infrastructure. That’s the kind of thinking that got us into this mess…
comment in response to
post
Kubernetes does a fairly good job at reducing the potential value added by public cloud vendors. With nothing more than the ability to create virtual machines, you can get a full cloud native infrastructure.
comment in response to
post
It’s a really weird domain. It seems like everybody who ever learns it has to stretch a bit :)
Come at it from a development perspective? You’ll need to learn Linux. Were you a sysadmin? You’ll need to learn programming.
One of the best guys I know at this has a degree in music…
comment in response to
post
You can get into architecture from a variety of different paths. Hand-in-hand with that is the fact that if you talk to three different architects about what they do, you’ll often get three very different answers, even when they work together ;)
comment in response to
post
Architect is another popular one
comment in response to
post
It’s possible we all will…
comment in response to
post
I have worked with teams that manage certain critical state services manually and terraform the stuff around it. They import using data blocks.
I have worked with teams that need to be able to create resources in terraform but never delete them. They use lifecycle policies.
comment in response to
post
Without a requirement for agentless, Ansible is probably the wrong tool.
comment in response to
post
At a certain point, you could just use docker on your VPS
comment in response to
post
With incredible amounts of patience on both sides
comment in response to
post
There’s a vibe. A spectrum of vibes, in fact.
comment in response to
post
I tell myself that I might need to retain windows for gaming but when I look at my life in the last three years, the number of times I played a game at all is depressingly low, let alone one that requires windows.
comment in response to
post
I wouldn’t consider salt with a minion equivalent to ansible. If you want broad agentless capabilities, you’re going to need to rely on something like python to be present by default, which is true of most Linux.
comment in response to
post
I agree with you, contributing to OSS would be what I recommend somebody who doesn’t get enough experience from work.
comment in response to
post
I wonder if there is an opportunity for improvement here. Maybe companies who provide Kubernetes as a service could have part of their value add be a local environment designed to be useful for people in your situation.
comment in response to
post
Software engineering cares for infrastructure now. If it weren’t Kubernetes, it would be something else probably more painful :)
comment in response to
post
Mine will be a dirge!
comment in response to
post
What would you do with it at home?
comment in response to
post
A good rule of thumb is if you can’t explain why something should be used for the task being designed, don’t use it.
comment in response to
post
Essentially, loops are a way of repeating instructions. Declarative languages don’t give instructions, instead enabling us to describe what we want.
comment in response to
post
The way I want it to work is to allow me to use prototyping imperatively, and once I’m confident I know what I want, build it in a non-prod environment using declarative IAC, and once I’m confident that does what I expect, schedule a change to do the same in production.
comment in response to
post
But I could build an API! And there can be messages, and Mongo…
comment in response to
post
I think people blur the advantages of automation with the advantages of a command line. If you’re not automating, the advantages of a command line are nuanced and situational. And the advantages of standard graphic UI include obviousness of function…
comment in response to
post
Purrs when it sees a bug, very useful
comment in response to
post
It’s super useful for infrastructure as code! That said, some types of services may still take a few imperative calls to the cloud provider API to work most efficiently. There’s also maintenance or one-off tasks that are normally best done imperatively.
comment in response to
post
They are immensely popular.
comment in response to
post
The best architects have a practical streak, where they’re capable of having any conversation on any subject, but they only will when it’s advancing the common interest.
comment in response to
post
comment in response to
post
Daemonless, but I’m concerned it may be haunted…
comment in response to
post
I’m not sure you can do that without breaking the declarative nature of most IaC. For example: a loop cannot be used to define desired state, because it’s imperative. It’s something you order a computer to do.
comment in response to
post
Nothing, in fact! And I’m glad to have learned about it. I only knew that OVH and Exoscale didn’t have true function as a service, and in hindsight should’ve looked up scaleway before replying :)
comment in response to
post
I don’t see any compelling serviceless options from non-Google/AWS/Microsoft cloud providers.
comment in response to
post
Wow I completely missed the word “images” in your post!
comment in response to
post
Serverless is going to tie you to them. You can make a cloud native application using a number of other technologies, but this really is their secret sauce.
comment in response to
post
The hyperscalers are all going to be US-based. If you want to get away from them, you may want to re-architect out of serverless. Is that an option?
comment in response to
post
I feel there will be two streams of software. One where we spend more cycles training language models to produce code that we can read, and one where we just give it an expected output and treat the code like a black box.