Articles: Cloud by Naasson
Clouds and platforms that stay with you
Cloud by NaassonBackups you can actually restore
A backup nobody has restored is a rumour. Where Cloud by Naasson makes restoring easier, and where the work stays yours.
What one purchase includes
Working infrastructure, not a starting point you then have to finish yourself. The contents and the limits.
Domains, certificates and the public-or-not decision
Every application in the catalogue carries metadata on how it authenticates and how it is published. It is not a description: it decides whether the application ends up on the internet.
One binary instead of a platform
Install is one command, update is replacing a file, removal is deleting a file. A platform you have to deploy in order to deploy infrastructure has a chicken-and-egg problem.
Install writes to the repository, not to the cluster
The install command does not mean "install now". It means "record that this should exist". ArgoCD does the installing, and that changes the meaning of every other operation.
An application update is a commit
The chart version is pinned in the repository. So an update shows up in the diff, a rollback is a reverted commit, and "it updated itself" becomes impossible.
Two hundred and seventy services, and not one of them interesting
Nothing in the catalogue is worth showing at a conference. That is the goal: infrastructure should be made of solved problems.
An alert nobody reacts to is worse than no alert
A channel with two hundred messages a month and not one action trains the team to ignore messages. That training then works during a real incident too.