We create digital products for a diverse set of (pretty large) customers (automotive, logistics & banking).
Now we are looking for a DevOps engineer to support one of our big client projects that is used by a lot of people daily.
Instead of predicting what will (not) happen these were some of the challenges in the past:
* advise the teams during the introduction of resource requests & limits
* supporting the decision of resizing the Kubernetes clusters on the requirements and factoring in operational cost
* integrating Azure KeyVault & EventHub into our backend services
* introduce Ansible to provision virtual machines
* introduce PostgreSQL monitoring and support a resizing decision
* analyze and research an issue with a Docker update
Our working language is German. All levels of proficiency are welcome!
Since I used to do the job feel free to ask me anything: a dot okeeffe at sprinteins dot com
For all positions take look at our jobs page and apply if you're interested: https://www.sprinteins.com/karriere/
Every time this happens, Xcode uses about 4GB of RAM (probably because of the monolithic UI storyboard of Lunar) but it should still leave enough memory for my other non-memory hungry apps.
But then I open Activity Monitor and I see WindowServer using ~80GB of memory [2]
The only remedy is either `killall WindowServer` or a full reboot.
I've been using an M1 MacBook Pro and Monterey since the first developer beta but this only became an issue in the last 2 months or so.
https://bugs.chromium.org/p/chromium/issues/detail?id=115840...
We create digital products for a diverse set of (pretty large) customers (automotive, logistics & banking).
Now we are looking for a DevOps engineer to support one of our big client projects that is used by a lot of people daily.
Instead of predicting what will (not) happen these were some of the challenges of the last six months:
* advise the teams during the introduction of resource requests & limits
* supporting the decision of resizing the Kubernetes clusters on the requirements and factoring in operational cost
* integrating Azure KeyVault & EventHub into our backend services
* introduce Ansible to provision virtual machines
* introduce PostgreSQL monitoring and support a resizing decision
* analyze and research an issue with a Docker update
Our working language is German. All levels of proficiency are welcome!
Since I used to do the job feel free to ask me anything: a dot okeeffe at sprinteins dot com
For all positions take a look at our jobs page: https://www.sprinteins.com/karriere/
google.*##.g:has(a[href*=".pinterest."])
google.*##a[href*=".pinterest."]:nth-ancestor(1)
duckduckgo.*##.tile:has(a[href*=".pinterest."])We create digital products for a diverse set of (pretty large) customers (automotive, logistics & banking).
Now we are looking for a DevOps engineer to support one of our big client projects that is used by a lot of people daily.
Instead of predicting what will (not) happen these were some of the challenges of the last six months:
* advise the teams during the introduction of resource requests & limits
* supporting the decision of resizing the Kubernetes clusters on the requirements and factoring in operational cost
* integrating Azure KeyVault & EventHub into our backend services
* introduce Ansible to provision virtual machines
* introduce PostgreSQL monitoring and support a resizing decision
* analyze and research an issue with a Docker update
Our working language is German. All levels of proficiency are welcome!
Since I used to do the job feel free to ask me anything: a dot okeeffe at sprinteins dot com
For all positions take a look at our jobs page: https://www.sprinteins.com/karriere/
But there are other vectors. With a VM you get a whole linux distribution, which of course increases the attack surface, but at the same time you also get much better isolation and that distribution's team of maintainers looking over your software, providing security patches, advisories, a simple way to update the system and so on. On the other hand there exist 'docker best practices' tutorials (not the posted one) that recommend not updating your base system at all in the name of reproducibility. Docker's solution to update management is manual image tagging and manual updates, possibly with help of external tooling. I don't think that's a good solution for that problem.
Imo the overall best solution is to run stuff in VMs and pick a lightweight distro for that.
That not updating part is of course just plain and simply bad advice.
What solutions for update management would you recommend in the VM space?