bbrennan

Fairwinds | Remote (US) | Full-Time

Fairwinds is looking for an SRE with Kubernetes experience.

As an SRE at Fairwinds, you’ll work directly with clients to ensure their goals are met through automation, analysis, and infrastructure configuration. Working collaboratively with the other SREs at Fairwinds, your expertise will help our clients succeed with Kubernetes through building robust infrastructure, solving complex problems, maintaining reliable, secure environments, and standing behind our work as a part of our on-call rotation.

https://www.fairwinds.com/careers/openings/site-reliability-...

Fairwinds | Senior Frontend Engineer (React) | Full-Time or Contract - $130-150k | fairwinds.com

https://boards.greenhouse.io/fairwinds/jobs/4776828003

Polaris maintainer here - happy to answer any questions!

Fairwinds | Site Reliability Engineer (SRE) | Remote | Full-time

https://www.fairwinds.com/careers

We're a provider of software and services focused on Kubernetes. We've been remote-first since our inception ~6 years ago, and have built an inclusive, learning-driven engineering culture. We're looking for someone with Kubernetes experience who likes working with customers and solving hard problems.

Fairwinds | Site Reliability Engineer | Remote (US) | Full Time

Fairwinds is a leading provider of Kubernetes software and services. We're looking for an intellectually curious, collaborative, enthusiastic, and flexible engineer to join our team as a Site Reliability Engineer.

https://boards.greenhouse.io/fairwinds/jobs/4196103003

Fairwinds | Remote | Frontend, Product, Sales

Fairwinds is creating Open Source and commercial software to help folks with Kubernetes. We're building an inclusive, remote-first culture with an emphasis on learning and growth. Come join us!

https://boards.greenhouse.io/fairwinds

Fairwinds | Full-Time | Remote | $85k-$180k

Fairwinds is a trusted provider of Kubernetes security and governance software. We're a remote-first organization, with a heavy focus on learning and growth.

We are hiring for two open eng positions:

SRE tech lead: https://boards.greenhouse.io/fairwinds/jobs/4728102003

Frontend Engineer (React): https://boards.greenhouse.io/fairwinds/jobs/4776828003

FYI - Polaris open source has both these things :)

(Disclosure - I'm a maintainer)

Fairwinds | Engineers | Remote (US)

We're looking for folks familiar with Kubernetes. Specifically:

* SREs to help us serve our clients

* A Kubernetes developer to help build k8s-focused software

Apply here: https://boards.greenhouse.io/fairwinds

Hey all - author here.

Just to clear up any confusion: Polaris is 100% free and open source, under the Apache 2.0 License

Some of the questions below pertain to a commercial product, Fairwinds Insights, which includes Polaris as a plug-in (as well as Goldilocks, kube-bench, kube-hunter, and others). While Insights is a separate (paid) product, it can help folks track the lifecycle of their Polaris findings, collate results across clusters, set up Slack/Datadog alerts, etc.

Sorry if that wasn't clear from the article - happy to answer questions about either!

Agreed per-node pricing is not ideal, but it appears to be an industry standard - most k8s tooling charges per node.

Since different clusters have different node profiles (in terms of size, scaling, etc), we offer discounts on per-node pricing when customers have a large number of nodes.

We're looking at building OPA support into Polaris as well, given how much the community has invested in it. For all the promise of OPA, we haven't seen it gain much traction outside of large enterprises, for many of the reasons we outline in the article.

Polaris is also 100% free. My guess is you're referring to Insights[0], which is a SaaS that incorporates Polaris, as well as several other open source auditing tools. We do offer per-node discounts for customers with a large number of nodes.

[0] https://www.fairwinds.com/insights

Popeye is a very cool project with the same general aim - it checks a lot of the same things as Polaris. It's very much CLI-first (and does an amazing job at that), while Polaris is happy to run as a CLI, a web dashboard, a validating webhook, or a CI/CD check.

kube-score I hadn't heard of, but looks very cool. You're right on matching resources - one of the requests we've gotten is to be able to check that every deployment comes with a PDB, which it looks like kube-score checks. Definitely a feature we're looking into!

Cue looks very cool! We hadn't heard of it when implementing custom checks, but looks like it would have been a contender

Good to know! I might adjust this to do it with a keystroke rather than a click. Anything to make a tedious process faster :)

Fairwinds | Full Stack | Golang, Kubernetes, Web | Full-time | REMOTE

Fairwinds (fairwinds.com), a leader in Kubernetes managed services and software is seeking a software developer to supplement the development capabilities of our SRE team.

You will be joining our first full-time development team, as part of a larger initiative to build our first commercial software offering. As one of the very first developers at Fairwinds, you’ll have ample opportunity for personal and professional growth as we ramp up our ability to serve the rapidly expanding Kubernetes market. You’ll work with a team to design, scope and execute features on a variety of projects. We work with Golang, Python, HTML/CSS/JS and Bash. Experience in one or more of those is expected. Bonus points for AWS or GCP experience, or Kubernetes.

Above technical skills, we value a candidate’s:

- Ability to iterate quickly and adapt to change - Ability to both work independently and collaborate with a team - Desire to contribute creatively to the product roadmap and user experience - Desire to learn new technologies in a rapidly evolving ecosystem

Diversity & Inclusion Statement:

Everything our engineering team does is guided by our core values: Respect, Inclusion, Compassion, and Kindness. We are good to each other and say ‘We don’t do that here,’ when someone is out of line. We also value diversity in our team. To us, a diverse team means we welcome people from different races, generations, geographical locations, gender minorities, people of color, members of the LGBTQIA+ community, individuals with disabilities and veterans. Building a diverse team is a moral imperative and we build a better business and product by bringing different perspectives to the table. We look for voices unlike our own because they are the ones that help us grow.

https://angel.co/company/fairwinds/jobs/316789-full-stack-de...

Here's the documentation for dealing with multi-instance scenarios: https://docs.one-db.org/Create_an_App/Multiple_Instances

If your data is hosted on a personal instance, you can "broadcast" that data to other instances - you just send them a link to where the data lives on your personal instance. The JavaScript client follows these links and collates the data in the frontend.

Hope that answers your question - happy to discuss further!

I'm amazed this doesn't already exist. But you're right there's no single source you can go to for a brief, unbiased description of even the top 50 tokens. If you can get the community going, I think this could be a big help.

Any plans to add live data?

Thanks! We've been distributing our code on GitHub for the last year or so, and wanted to put a more formal mechanism in place to manage payments and access control.

I'm still not sure how many people currently use GitHub to distribute proprietary software, but it works very well for us. Clients are able to submit issues and pull requests, and are much more engaged than if we just emailed them a zip file.

I don't think anyone is arguing that machine readable specs should take the place of human readable documentation. Specs are helpful for testing, integrations, and generating HTML docs.

I agree the API provider's primary concern should be Developer Experience, and understand why creating a spec often takes a back seat. But I suspect that soon it will be seen as critical for any production grade API to have a machine readable spec.

I view specs as analogous to unit tests - it doesn't get you closer to a deliverable product, but it makes the development lifecycle much less painful.

I actually have two related projects here:

Scrape HTML to swagger: https://github.com/bobby-brennan/scrape-to-swagger

Swagger to HTML docs: https://github.com/lucybot/lucy-console

We also have a commercial version of the latter which you can see at any-api.com

Yes! Over 200 specs are provided for free by APIs.guru:

https://github.com/apis-guru/api-models

Having a machine readable spec is important for driving examples though. For instance, at LucyBot we use OpenAPI to drive Recipes - tutorials for using an API to achieve a specific use case. Each recipe provides working sample code in a few different languages. You can see examples for Kaltura's video API at developer.kaltura.org

That's a great idea. So far we've had mixed success posting solutions to specific problems (e.g. sync your github issues to a spreadsheet), but each solution only appeals to some small subset of people, and doesn't convey the enormity of the set of problems DataFire can solve. A higher level post that uses DataFire to solve multiple problems aimed at a single goal would do more to stimulate people's imaginations.

We built DataFire (DataFire.io), a cloud-based framework for working with APIs. Similar to zapier but geared toward developers (and as a consequence 10x more powerful).

We've gotten a lot of engagement and positive feedback from existing users, but after the initial launch haven't seen as much growth as we'd like. What can we do to attract new users?

I've been working on a web-scraping tool for API documentation, scrape-to-swagger

https://github.com/bobby-brennan/scrape-to-swagger

I built something similar because I was disappointed with what was already out there:

https://github.com/lucybot/jammin

I came across another CRUD package recently that seemed to have a good amount of momentum, but can't seem to find it now...

Thanks for the feedback! We're hard at work on v2, and will definitely include something like this.

Hey all, founder here. We've just opened up the DataFire beta and are looking for feedback.

Would love to hear any thoughts or requests!

Sorry, not sure I understand. Display what?