Played some Eurobeat on Spotify and that was fun keeping time to the beat. Annoyingly Spotify removed the running mode which allowed me an auto-playlist of specific BPM tracks. Now I have no idea what music to play to help keep pace. Spotify have added some static playlists giving a range of BPM, but that doesn’t work as well.
c25k training. A relatively warm but not overly-hot today. Week 3 runs. 1.5 min run/1.5 min walk, then 3.0 min run/3.0 min walk, then repeat for 4 run/walk intervals.
Felt worked out, but not overly pushed for some reason….
FitBit and ZenLabs were in disagreement about the distance I ran again – ZenLabs said 4.1 km, FitBit said 3.59
Nice sunny day for running, but my Fitbit Blaze kept losing it’s connected GPS to my phone. My previous watch (Surge) had inbuilt GPS so this didn’t happen. Possibly the FitBit service was being killed because of Spotify….
Sad news that M$ are to acquire GitHub. I suspect I’ll start getting Windows adverts in my email inbox soon as my office uses GitHub
On the plus side, this LinuxJournal article has proposed some alternatives. GitLab is a good one and even mentioned on some job listings so I guess I’ll move my repos there.
One of the questions in my CKA exam was how to display taints with kubectl. While you can use kubectl describe, it creates a lot of other information too.
Then I found out about jsonpath and it’s similarity to jq
You can display the taints with something like
[code lang=text]
for a in $(kubectl get nodes –no-headers | awk ‘{print $1}')
do
echo $a – $(kubectl get nodes/$a -o jsonpath='{.spec.taints[].key}{":"}{.spec.taints[].effect}')
done
So the first one has a taint (it’s the master node) and the second one doesn’t.
(maybe I need to hack this a bit more when I have multiple taints but I’ll do that when I have some multi-tainted nodes to play with)
EDIT: Another way as provided by tdodds81
[code lang=text]
$ kubectl get nodes -o=custom-columns=NAME:.metadata.name,TAINTS:.spec.taints
NAME TAINTS
ip-10-10-10-148.eu-west-2.compute.internal [map[effect:NoSchedule key:node-role.kubernetes.io/master]]
ip-10-10-10-218.eu-west-2.compute.internal
ip-10-10-10-239.eu-west-2.compute.internal
ip-10-10-10-249.eu-west-2.compute.internal
ip-10-10-10-51.eu-west-2.compute.internal
[/code]
And with multi-taints, it looks like this (on a GKE cluster)
Well, exam is done – for the most part it went okay. A few questions were a bit ambiguous and there were several regarding etcd and low-level tinkering with the kubelet – which I hadn’t had too much experience with unfortunately. I’m hoping I did OK, though…
With less than 24 hours to go before my exam, I’m going to spend those last hours going through the review questions and see if I can still remember the content.
There is a new story doing the round about how Twitter found that it had stored user’s password in the clear in an internal log. Whilst reading it, I got this email from Twitter:
While this isn’t the first time a big company has done this (Github for one also did this), it seems unbelievable that a big company like Twitter would get itself caught out by this basic, common sense security practice. Pretty much every YouTube video and article about correctly handling passwords will tell you not to store them in the clear and only store them as hashes (with salts, preferably). Hashing algorithms are meant to be really difficult or impossible to reverse, meaning you can’t (easily) use the hashes to determine the original passwords.
Some examples from a quick YouTube search – Tom Scott’s video’s really good btw :), although is comment about “using login using Twitter and let them store your password for you” is a bit ironic :P
The fact that Twitter has our unencrypted passwords on disk… does this mean Twitter has been saving our original passwords before hashing them?
More to the point - whilst Twitter are quick to point out that no-one at the company can see the masked password, they don’t mention who has (or had) access to the unmasked passwords in the internal log. Or for how long…
Twitter users who had their accounts on private may not have been as private as they initially thought….
Durian has had a reputation of being a stinky fruit and it’s a well-deserved reputation. This fruit has a smell that can carry over a mile. Literally, on a visit of Malaysia, you could tell when there was a roadside stall selling Durian coming up by the smell.
However, in my opinion, the smell of Durian and the smell of gas are not alike at all…
And here’s what a Durian looks like if you’ve never seen one before…