wernerb

I can't edit my above comment anymore but I see that at least alerting is now a separate system in grafana 8! Great, we will take a look again!

Alert templating. Grafana is fussy about configuring alerts on dashboards that have variables. What this means is if you have 30 clusters and want to use a single dashboard with a drop-down variable seefting your cluster you cannot define alerts on it. It will refuse to do it.

Alerts are also integrated tightly in dashboards. Forces alerts to be saved/backedup/imported as single json blob. We want separate management of alerts so they can be defined as code and not in the dashboard blob of json!

What makes me chagrined is because of the above issues we have to use prometheus alert manager instead while our colleagues absolutely LOVE grafana itself! We can't duplicate alerts tens of tens times. We don't want that management nor do we want to teach our colleagues jsonnet/ksonnet to generate it. We also don't want permission problems.

Alert templating. Grafana is fussy about configuring alerts on dashboards that have variables. What this means is if you have 30 clusters and want to use a single dashboard with a drop-down variable seefting your cluster you cannot define alerts on it. It will refuse to do it.

Alerts are also integrated tightly in dashboards. Forces alerts to be saved/backedup/imported as single json blob. We want separate management of alerts so they can be defined as code and not in the dashboard blob of json!

What makes me chagrined is because of the above issues we have to use prometheus alert manager instead while our colleagues absolutely LOVE grafana itself! We can't duplicate alerts tens of tens times. We don't want that management nor do we want to teach our colleagues jsonnet/ksonnet to generate it. We also don't want permission problems.

In one episode even the ship needs therapy

Wireguard is performant, tailscale makes it convenient

I was under the impression that the softer plastic cant be recycled (isn't worth it) and goes directly to the landfill. The harder plastic is worth more (barely) and has a larger chance of being recycled back into pellets.

Seems to be fixed again?

Meet, and search very slow as well

What you suggest does scale with performance but not with organization its why Vault is used in the first place.

When I saw "secret store" I guessed it had to be Vault. Vault's is amazing but it lets you configure things that can blow up on you in X time. For example, issuing 50 secrets per second but have every secret expire after a week (or never). It would mean (multiple) goroutine per secret checking status on the lease. This kind of thing unfortunately, is easy to miss and occur in Vault.

The reasoning you put in also means kubernetes is unsuited to be controlled by terraform. Too many lifecycles (resources) to centrally control. kubernetes custom resources can have dependencies on others which terraform either needs to support as well. Which is not doable to maintain.. keep your kubernetes manifests outside or your terraform state.

I am honestly wondering more about your specific use case. Does the CPU cost outweigh the storage cost? Is it a timing problem (speedup) or are you at such large scale (on premise)?

Maybe where I'm getting at is, I can think of 99 problems but docker gzip ain't one :) how was this a priority (at some point)

Installing Yet Another Agent on your cluster/VMS and ensuring they are updated while the SSM agent got an upgrade I believe from python to go it still does a lot more than just provide ssh sessions correct?

It's even better! You sign a contract with denuvo for how many days protection. The less days the less you pay. When the contract is up they remove it

Just take a look at the gitlab ci reference. It is huge. And there are competing features in there that are intended to "deprecate" the older feature but this doesn't happen. They are also constantly held back on providing backwards support. For instance, adding dpeendency-like flow as opposed to stage based flow has been added but it's not possible to model dependencies from same stage making the whole thing kind of useless.

Versioning the yaml specs/apis is the correct move. I hope future CI systems take note.

This sounds like something that could be applied during pumping already (sewage treatment).

Love using qutebrowser. Really an amazing opensource browser! The only extension necessary for me was adblocking and now it's even better!

I did/continue to have issues with qt-webengine though, like 144hz monitor with qt webengine is limited to 60hz but these things are unrelated to qutebrowser. In fact most of my "bugs" can be related to upstream qt webengine and wayland support. I feel bad for the authors of qutebrowser for so often getting issues that is actually an upstream bug in qt. It doesn't help that qt webengine work is rather slow (imo)

There's magic about pressing "o" and typing in what you want to search from history or Google which is so fast and efficient. I have tried similar setups on other browsers but in qutebrowser the search algos are so simple and snappy, it works great. My colleagues sometimes were amazed at how fast I could navigate across the browser all thanks to this great software

Thank you qutebrowser!

It is sad to me you actually need linkers/istio for this. EndpointSlices support topology labels which the article states is in vanilla kubernetes. Which means you can create different services for example a zone. Like "myservice-eu-west1a".

The problem is that a pod has no easy way to know what topology it is in to make the choice to go to myservice-eu-west1a. The feature for getting topology labels through the downward api is not there! A pod has no idea where its scheduled!

The only way to find out is to ask the kubernetes api, but this requires rbac, a client, libraries etc.. unacceptable! Guess what linkerd does for you?

I am glad for the feature linkerd offers as it solves a problem and I can see the benefit of perhaps doing latency based routing as well on top of this.

It just ticks me off we need something complex to do something simple: keep workloads to their own zone depending on where they are.

Would something like the SHARC work? https://thenaudio.com/

Not american, but I believe it was said that this election you won't see the final results perhaps days/weeks even after election. Due to mail in votes I think?

This is incredibly frustrating, I can sympathize. But this is why we do backups even on cloud storage. I had the same thing happen with an EBS volume on AWS becoming unresponsive, unable to attach and load.

> The witness also stated they were asked by Morales to steal the nappy of a baby that regularly visited Assange, to establish paternity.

Wow.

Did you read the article? It is noted assange was scared a password leaked by the guardian could be used to unlock wikileaks unredacted content and would go out of control.

When I first read your comment I assumed case files or something were leaked, this is not about that.

The 80€ games are a bit of a shock. This makes deciding between all digital (hello permanent 80 euro prices!) and drive edition something to contemplate.

With this large price difference they are betting on a larger digital only share which will shrink the physical disk market.

The problem is that all IAM conditionals just give a generic "Denied" statement which is hard to debug. You at left figuring out if you are missing a uppercase character in your tag key. AWS IAM is currently not meant to be used in a devops/enforcement of best practices way. They have AWS config for that, but that's always after the fact while immediate feedback is what you need to function at scale.

A possible fix is to allow custom deny reasons but large changes like this to any already extremely large and entangled system like IAM is unlikely.

I should mention that the kubelet is plenty resilient for what it does. If at some point kubelet can connect again it will rejoin the cluster.

The API server is stateless and should be loadbalanced. The kubelet should be set to restart on failure and is not resilient. It keeps trying to connect to your API server and update its status if it can't it will keep retrying. The controller manager will remove the node after X minutes of no response.

My Dell XPS 13 has Linux support. Dell even sells the laptops with Ubuntu on it. The new 2020 edition called Dell xps 13 9300has a larger screen, better hinge and a webcam that doesn't look up into your nostrils. The only thing not working is the fingerprint sensor.

Turned off the "feature" as soon as Tv was on. Have been advising friends and adjusting their expensive oled TV's as well. In every case they were grateful for me "fixing" their TVs which only took a few minutes.

People just don't want to muddle around in the settings. And here lies the problem. It would be great if manufacturers would open up their interface settings to be influenced more easily by mediaplayers or settup boxes. Those in turn, could have a ruleset: if 24p, then disable motion blur if else enable motion blur. If sports enable motion blur. And so on.

It's not even limited to motion blur, I have low light and normal light profiles I'd like to have changed automatically based on the actual light in my room.

Paul Bettany (Jarvis from Iron man) claimed he did not watch the iron Man movies either. [0]

[0]: https://www.cinemablend.com/new/Paul-Bettany-Says-He-Never-S...