Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
wdella
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
wdella
2y ago
> I was surprised while digging up the link that Gravatational is still releasing v13 and v14 updates under Apache 2, so maybe even Teleport will continue to have legs for those who cannot deploy AGPL stuff Teleport puts out 3 major rele
2.
▲
Teleport relicenses from Apache to AGPLv3
(github.com)
3 points
by
wdella
3y ago
|
0 comments
3.
▲
by
wdella
4y ago
Disclaimer: I'm a Teleport employee, and participate in hiring for our SRE and tools folks. > A rubric written in advance that would allow a single person to vet a work sample response mostly cures the problem you have right now. Th
4.
▲
by
wdella
5y ago
Hi Bill, You mention "Product Designer (Senior, Lead, Principal or Director)" above, and I've got a friend (ex-Bing) interested in a Senior/Lead role. However https://duckduckgo.com/hiring doesn't
5.
▲
by
wdella
5y ago
For excellent reporting on a dystopian intersection of tech and politics: Darknet Diaries Episode 100: NSO On a different note: a whimsical, impossible, and hilarious improvised musical: Mission to Zyxx Episode 507: A Little ‘Ditty about Ja
6.
▲
by
wdella
5y ago
Tailscale and Teleport are similar, but operate at different levels of the network stack. Tailscale governs access and routing at L3 in the OSI model. See Hashicorp's Boundary or VPNs for alternatives. As a generalization, Teleport wor
7.
▲
by
wdella
5y ago
Roughly a year ago (November 2020): https://goteleport.com/blog/gravitational-is-teleport/
8.
▲
by
wdella
5y ago
Ever since Vagrant, everything Hashicorp has developed has been outstanding! Furthermore, their open core model and this S1 is an inspiration. I wish all the best for Mitchell, Armon and the team! I have a couple emails from Mitchell H circ
9.
▲
by
wdella
5y ago
> Did you also consider some form of out-of-band approval mechanism for production environment access? No, not before your comment at least. Vendor CI tools (be it GitLab, Drone, etc) often make it difficult to use this workflow. Their
10.
▲
by
wdella
5y ago
Hi! I wrote this. I’m happy to answer any questions.
11.
▲
by
wdella
5y ago
> How can they be avoided without stopping the use of CI/CD? Use separate systems for CI and CD, and don't put sensitive "keys to the kingdom" credentials in CI. For example: Put CI in GitHub Actions or GitLab CI wit
12.
▲
by
wdella
5y ago
> the CI system basically had admin access over our infrastructure. It has to in order to do infrastructure as code. > Public CIs are fine though. Ones that literally only do code builds, tests etc I couldn't agree more. Even int
13.
▲
by
wdella
7y ago
The Roman Mars Mazda Virus from Reply All and 99% Invisible. This joint episode is an engaging and hilarious tale of debugging an overly ‘smart’ car stereo, as well as going above and beyond the call of duty out of sheer love for podcasting
14.
▲
by
wdella
7y ago
I second “On the Metal”. My favorite episode thus far is Kenneth Finnegan on starting the Freemont Cabal Internet Exchange. A well told and empowering story of grassroots community building. Makes me want to get an ASN. https://o
15.
▲
by
wdella
7y ago
I'm an established Developer & SRE familiar with multi-datacenter cloud ops. Office dogs are a big perk for me! Location: Seattle Remote: Yes Willing to relocate: No Technologies: Python, Java, SQL, Shell/Linux, Cloud SOA. See
16.
▲
by
wdella
7y ago
I'm an established Devops/SRE familiar with large enterprise and multi-datacenter cloud ops. Office dogs are a big perk for me! Location: Seattle Remote: Yes Willing to relocate: Yes Technologies: Python, Java, SQL, Shell/Li