text stringlengths 0 1.8k |
|---|
**Gerhard Lazu:** A few years back, we were missing this. But we don't know what they have or don't have this year, or maybe what we're missing. Maybe they don't even know what we would like for them to have. And listeners of this show, they can think "You know what - this show is really interesting, because they are u... |
**Jerod Santo:** Right. |
**Gerhard Lazu:** So in a way, we're just producing good content. That is very relevant to us, when we say "You know what - we are informed, and we have made an informed decision to not use Cloudflare because of these reasons... Which may or may not apply to you, by the way." |
**Jerod Santo:** Right. It's like there's a brand new hammer, and we grab hold of it... And everyone gathers around, we put our hand out and we strike it right on our thumb. And then everybody knows "That hammer really hurts when you strike it on your thumb. I'm glad those guys did it. I've learned something. I don't h... |
**Gerhard Lazu:** \[laughs\] I think that's a very interesting perspective, but I don't see it that way. It's an amazing analogy, but I'm not sure that it applies here... But it's great fun, that's for sure. |
**Adam Stacoviak:** yeah. |
**Jerod Santo:** Okay, good. |
**Break**: \[19:48\] |
**Gerhard Lazu:** So you were asking, Jerod, what is next on our hill... One of the things I learned from the Fastly incident is that we don't have anything to manage incidents. When something is down, how do we let users know what is going on? How do we learn from it in a way that we can capture and then share amongst... |
A document is great, a Slack just to write some messages is great, but it feels very ad-hoc. So one of the things that I would really like is a way to manage these types of incidents. And guess what - there's another incident that we have right now. |
**Jerod Santo:** Right now? |
**Gerhard Lazu:** Right now, right now. |
**Jerod Santo:** Like the website's down right now? |
**Gerhard Lazu:** No. The incident - this is a small incident... |
**Jerod Santo:** Okay, good... |
**Gerhard Lazu:** No, the website is 100% up. |
**Jerod Santo:** 100% uptime, thank you. |
**Gerhard Lazu:** Yeah. So Fastly, it's your responsibility to keep it up, right? That's what it boils down to. It's someone else's problem. It's Fastly's problem. |
**Jerod Santo:** That's right. Pass the buck. |
**Gerhard Lazu:** Right. So right now, one of the DNSimple tokens that we used to renew certificates has been deleted. So it's either Adam or Jerod, because I haven't. |
**Adam Stacoviak:** It wasn't me... |
**Gerhard Lazu:** Anyways, I'm not pointing any fingers... |
**Adam Stacoviak:** I don't touch DNS. |
**Gerhard Lazu:** So in the account -- |
**Jerod Santo:** It's looking like maybe it was me, but I haven't touched anything, so I don't know what's going on. It could be worse than we think. |
**Adam Stacoviak:** It could be a bit flip. |
**Gerhard Lazu:** So we had two DNS tokens, one was for the old setup and one was for the new setup. The one for the old setup I have deleted, because we just didn't need it... And then we had three DNS tokens left. One of them disappeared. It's no longer there. And that was the one that was used by cert-manager to ren... |
Now, I've found out about this by just looking through K9s what is happening with the different jobs. There's jobs which are failing, that are meant to renew things. It's not the best setup, so the first thing which I've done, I've set up an alert in Grafana Cloud, when the DNS expires in less than two weeks, or in act... |
So what I would like to do is first of all capture this problem in a way that we can refer back to it, and also fix it in a way that we also can refer back to it, like how did we fix it; what went into it, what was added, so that this doesn't happen again. And adding that alert was one of the actions that I took even b... |
**Adam Stacoviak:** Was it called an access token? |
**Gerhard Lazu:** Yes. |
**Adam Stacoviak:** \[23:56\] So on June 19th -- they have an activity log. This is actually kind of important for -- I think this is super-important for services that have multiple people doing things that are important, that could break things, essentially... Have an activity log of things that happened - deletions, ... |
**Jerod Santo:** So we don't know what happened. |
**Adam Stacoviak:** Well, we do, for the past 30 days. So on June 19th, because I'm the only user, it says "Adam deleted it." So I guess I "deleted" it, but it was not me. |
**Jerod Santo:** Hah, so it was you. |
**Gerhard Lazu:** No, that was actually me... But the token which I deleted was the one for the old infrastructure. There were two tokens. |
**Adam Stacoviak:** I see, okay. So this happened -- do you know when, roughly? Can you assume at least? |
**Gerhard Lazu:** June 19th sounds right. But a single token was deleted and we had two. |
**Adam Stacoviak:** Yeah, okay. So it shows a single token being deleted June 19th, at an abnormal time for me to do any deletions. I think Jerod as well. |
**Gerhard Lazu:** Yeah, that was me. |
**Adam Stacoviak:** If this is Central timezone, because that's where I'm at \[unintelligible 00:25:04.28\] it's 7:16 in the morning. I'm definitely not deleting things at that time besides Z's in my brain. I don't get up that early. That's how we know. |
**Jerod Santo:** Maybe you accidentally deleted two. It was a two for one deal that morning. |
**Adam Stacoviak:** It doesn't show on the activity log though, so that's the good thing. |
**Gerhard Lazu:** Right. |
**Adam Stacoviak:** I would maybe push back on DNSimple support and they can dig into it. And then 1) get a true git-blame on this, and then 2) see if it was maybe just an error on the platform side. |
**Jerod Santo:** Yeah, I don't think I've done anything with tokens aside from maybe one of our GitHub access tokens was expiring, or they've made a new one and I think I rotated one token... But nothing to do with DNS. Not in the last month, or six months. |
**Adam Stacoviak:** It'd be cool if certain things like this required consensus. You can delete it if Jerod also deletes it. |
**Jerod Santo:** It's like the nuclear codes. You've gotta have two hands on the button. |
**Adam Stacoviak:** Yeah. You don't have to do it at the same time. You can do it async by saying "Okay, Gerhard, at his 7 in the morning timeframe (because he's in London) deleted it." You get an email, Jerod, saying "Gerhard deleted this. Do you wanna also have consensus on this deletion?" and you have to go and also... |
**Jerod Santo:** It seems awfully draconian for a DNS access token. That's why I think the nuclear codes makes sense... You know, like, you're about to send a nuclear bomb, you've gotta have consent. But I think an access log is good enough. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.