profile
viewpoint
Joe Beda jbeda @VMware @heptio Seattle, WA http://www.eightypercent.net Principal Eng @vmware via @heptio. Also founded @kubernetes, @spiffe and GCE.

jbeda/docker-postfix-forwarder 19

Docker container image for implementing a postfix forwarder using postfix.

jbeda/go-jsonnet-old 5

A pure Go port of jsonnet

jbeda/dotfiles 4

My personal dotfiles

jbeda/bedafamily 2

Source for bedafamily.com

issue closedvmware-tanzu/tgik

Episode Idea: Using bitnami sealed secrets

It would be cool to dive into Bitnami sealed secrets in a future episode:

https://github.com/bitnami-labs/sealed-secrets

Key security, rotation and management would be cool things to play with.

closed time in 12 days

Matty9191

push eventvmware-tanzu/tgik

Joe Beda

commit sha ff295df291d5ec9f9ae4bcfeb8cea3462962d9da

Episode 132 Signed-off-by: Joe Beda <joe.github@bedafamily.com>

view details

Joe Beda

commit sha 6375d18a8dea7c057239e8614ab8fc2930638ab6

Merge pull request #314 from jbeda/132 Episode 132

view details

push time in 12 days

PR merged vmware-tanzu/tgik

Episode 132
+58 -1

0 comment

3 changed files

jbeda

pr closed time in 12 days

PR opened vmware-tanzu/tgik

Episode 132
+58 -1

0 comment

3 changed files

pr created time in 12 days

create barnchjbeda/tgik

branch : 132

created branch time in 12 days

issue commentvmware-tanzu/tgik

Episode Idea: Using bitnami sealed secrets

Yup! going to do it this week.

Monday or Tuesday:

  • [ ] Pick a topic and create/use an issue in the repo
  • [ ] If applicable coordinate with an upstream project if they're interested in attending the show
  • [ ] Create the graphic
  • [ ] Schedule on Youtube
  • [ ] Add scheduled episode to TGIK playlist on YT
  • [ ] Create short link in rebrandly
  • [ ] Tweet about it from your personal account
    • [ ] Post tweets on internal #tgik slack channel and cc @castrojo and Vykky
    • [ ] Get confirmation from boschem that she's seen the tweet and is scheduling it

Before episode:

  • [ ] Create HackMD page for live notes. Start with README template in this repo
  • [ ] Paste HackMD URL on internal #tgik channel and cc @castrojo or other assistant
    • [ ] Assistant adds ~5-10 news items from around the web as possible "News of the Week"
  • [ ] Get everything tested well before episode so you can debug
  • [ ] Use internal slack channel to ensure that AV setup is good

After show (ideally right away but can wait until Monday):

  • Create/submit PR for this repo
    • [ ] Episode directory and README from hackmd
    • [ ] Any other files from the episode that might be useful
    • [ ] Update playlist.md with episode
    • Feel free to self merge
  • [ ] Edit YT description to point to episode directory here
  • [ ] OBS/OS Upgrade if applicable (Never on the day of a show)
Matty9191

comment created time in 14 days

issue commentvmware-tanzu/tgik

Episode Idea: Using bitnami sealed secrets

Hrm! I thought we did an episode on sealed secrets but I htink that may have been a live one at a kubecon.

Matty9191

comment created time in 15 days

pull request commentkubernetes-sigs/cluster-api

:seedling: Add Cluster API icons to repo

Go for it! Would love to see these be included. Let me know if you need any tweaks. Happy to see these be included with the rest of these icons with the same license.

detiber

comment created time in a month

issue commentcloudfoundry/cf-for-k8s

cf-for-k8s should support a great and easy first time / trial experience

Commenting from the outside. I'm not a super active member of the community here. But I was responsible for helping to standardize on ytt/kapp on the VMware side (and continuing to invest in those tools over time). I think that had a great influence on the choice here as part of this project.

While Helm has wide adoption, I personally am not a fan of the way that deployment and templating are tightly coupled. And, as a former member of the CNCF TOC, projects that are incubating or graduated are not the solution but rather a solution that has met a bar wrt security, maturity, governance and adoption. The CNCF is totally ok with competing projects and publicly aims not to be a "kingmaker".

On the technical issues here -- there is no silver bullet here.

The fact that ytt and kapp are two separate tools really enables people to integrate this with other workflows. For instance, the monolithic nature of helm creates problems with using it with gitops as having separate render and apply steps is much more natural (and fits with other tools in the space like kustomize or jsonnet or cue). helm template often has issues for more advanced helm charts. (Sidebar: I was talking to one of the main authors of the GitOps toolkit - https://github.com/fluxcd/toolkit - and he mentioned that they had to special case Helm for these reasons.)

Beyond that, the go template engine that helm uses is uniquely unsuited for templating YAML. Text based templatization is super error prone with a whitespace sensitive document. You can see this in something like the nginx chart.

IMO the ytt strikes a good balance between something that is structure aware, very portable without custom binary extensions and approachable in terms of using a variant of a popular language (starlark/python). Again, there is no silver bullet in this space and there will always be pros and cons to any solution.

Talking to the ytt team, they are taking the feedback that you gave above seriously and would like to smooth over those rough edges. I encourage you to file some issues over at the ytt repo. The team would love to engage on those specifics.

From my point of view -- I think that providing a fully rendered set of yaml with good defaults is a great thing for a project to have and I'd encourage that. It makes it easy for folks to get started without having to use a common toolset and is something I personally love to see in projects.

Finally, I trust that the folks working on cf-for-k8s have users at the top of their minds and are weighing off different options here as decisions like this are made. At the end of the day, in open source, technical decisions, when reasonable people can disagree, are made by those on the ground doing the work.

cmoulliard

comment created time in 2 months

startedfluxcd/toolkit

started time in 2 months

issue closedvmware-tanzu/tgik

Vertical Pod Autoscaling

https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler

In general how to set requests/limits and what that might look like going forward.

closed time in 2 months

jbeda

push eventvmware-tanzu/tgik

Joe Beda

commit sha 895df195ada2a43e3f9f4ddb37437d18dc78459b

Notes and files for 126 Signed-off-by: Joe Beda <joe.github@bedafamily.com>

view details

Joe Beda

commit sha 18331326a81e5c56ac591e4e998f5f7b3e1b806e

Merge pull request #304 from jbeda/126 Notes and files for 126

view details

push time in 2 months

PR merged vmware-tanzu/tgik

Notes and files for 126
+255 -0

0 comment

5 changed files

jbeda

pr closed time in 2 months

PR opened vmware-tanzu/tgik

Notes and files for 126
+255 -0

0 comment

5 changed files

pr created time in 2 months

create barnchjbeda/tgik

branch : 126

created branch time in 2 months

issue commentvmware-tanzu/tgik

Vertical Pod Autoscaling

From @embano1: https://twitter.com/embano1/status/1257779994664861696. Some analysis on Autopilot and pointer to Cindy's take.

jbeda

comment created time in 2 months

issue commentvmware-tanzu/tgik

Vertical Pod Autoscaling

Also from Duffie: https://medium.com/infrastructure-adventures/vertical-pod-autoscaler-deep-dive-limitations-and-real-world-examples-9195f8422724

And folks often use the kube-prometheus and the prom adapter to populate the metrics api in kube https://github.com/coreos/kube-prometheus/tree/master/manifests

jbeda

comment created time in 2 months

issue commentvmware-tanzu/tgik

Vertical Pod Autoscaling

From Duffie: we need to add these two lines to the components.yaml from metrics-server to support kind https://gist.github.com/mauilion/cd10204e924600c15c5c14c97c2ca66b#file-components-yaml-L91-L92 cause the hostnames of the nodes aren't resolvable from the metrics-server pod. and because the serving certs for the kubelet are self signed. (edited)

From Jorge: Office hours video talking about VPA -- https://www.youtube.com/watch?v=5kJ6tJXq-qU&feature=youtu.be&t=2558

jbeda

comment created time in 2 months

issue commentvmware-tanzu/tgik

Vertical Pod Autoscaling

Also Google paper on autopilot: https://dl.acm.org/doi/pdf/10.1145/3342195.3387524

jbeda

comment created time in 2 months

issue commentvmware-tanzu/tgik

Vertical Pod Autoscaling

https://github.com/FairwindsOps/goldilocks is relevant.

jbeda

comment created time in 2 months

issue commentvmware-tanzu/tgik

Vertical Pod Autoscaling

https://studio.youtube.com/video/p6zCzyBNhLE/livestreaming

jbeda

comment created time in 2 months

issue commentvmware-tanzu/tgik

Vertical Pod Autoscaling

Monday or Tuesday:

  • [ ] Pick a topic and create/use an issue in the repo
  • [ ] If applicable coordinate with an upstream project if they're interested in attending the show
  • [ ] Create the graphic
  • [ ] Schedule on Youtube
  • [ ] Add scheduled episode to TGIK playlist on YT
  • [ ] Create short link in rebrandly
  • [ ] Tweet about it from your personal account
    • [ ] Post tweets on internal #tgik slack channel and cc @castrojo and Vykky
    • [ ] Get confirmation from boschem that she's seen the tweet and is scheduling it

Before episode:

  • [ ] Create HackMD page for live notes. Start with README template in this repo
  • [ ] Paste HackMD URL on internal #tgik channel and cc @castrojo or other assistant
    • [ ] Assistant adds ~5-10 news items from around the web as possible "News of the Week"
  • [ ] Get everything tested well before episode so you can debug
  • [ ] Use internal slack channel to ensure that AV setup is good

After show (ideally right away but can wait until Monday):

  • Create/submit PR for this repo
    • [ ] Episode directory and README from hackmd
    • [ ] Any other files from the episode that might be useful
    • [ ] Update playlist.md with episode
    • Feel free to self merge
  • [ ] Edit YT description to point to episode directory here
  • [ ] OBS/OS Upgrade if applicable (Never on the day of a show)
jbeda

comment created time in 2 months

push eventjbeda/dxf2svg

Joe Beda

commit sha 2c6662c10af6cc91d70a503028269676860a5bf6

Fix arc, debug logging Signed-off-by: Joe Beda <joe.github@bedafamily.com>

view details

push time in 2 months

push eventjbeda/dxf2svg

Joe Beda

commit sha 2505fa0cdfb117423473c0c401a77c757c00518f

Add PolyLine and LWPolyLine Signed-off-by: Joe Beda <joe.github@bedafamily.com>

view details

push time in 2 months

push eventvmware-tanzu/tgik

Joe Beda

commit sha f629c36d644b091013e35dea65f899e65425135e

Notes for 124 Signed-off-by: Joe Beda <joe.github@bedafamily.com>

view details

Joe Beda

commit sha a8b6f5a6e886af5f20bf257257fb07ee9114f5f9

Merge pull request #298 from jbeda/124 Notes for 124

view details

push time in 2 months

PR merged vmware-tanzu/tgik

Notes for 124

Fixes #240

+66 -0

0 comment

2 changed files

jbeda

pr closed time in 2 months

issue closedvmware-tanzu/tgik

Episode idea: KUDO

KUDO is the Kubernetes Universal Declarative Operator. https://kudo.dev/

closed time in 2 months

jsarkar

PR opened vmware-tanzu/tgik

Notes for 124

Fixes #240

+66 -0

0 comment

2 changed files

pr created time in 2 months

create barnchjbeda/tgik

branch : 124

created branch time in 2 months

issue commentvmware-tanzu/tgik

Episode idea: KUDO

https://hackmd.io/cNRuv5jvRVuvIbCpbKScMA?view

jsarkar

comment created time in 2 months

issue commentvmware-tanzu/tgik

Episode idea: KUDO

Monday or Tuesday:

  • [ ] Pick a topic and create/use an issue in the repo
  • [ ] If applicable coordinate with an upstream project if they're interested in attending the show
  • [ ] Create the graphic
  • [ ] Schedule on Youtube
  • [ ] Add scheduled episode to TGIK playlist on YT
  • [ ] Create short link in rebrandly
  • [ ] Tweet about it from your personal account
    • [ ] Post tweets on internal #tgik slack channel and cc @castrojo and Vykky
    • [ ] Get confirmation from boschem that she's seen the tweet and is scheduling it

Before episode:

  • [ ] Create HackMD page for live notes. Start with README template in this repo
  • [ ] Paste HackMD URL on internal #tgik channel and cc @castrojo or other assistant
    • [ ] Assistant adds ~5-10 news items from around the web as possible "News of the Week"
  • [ ] Get everything tested well before episode so you can debug
  • [ ] Use internal slack channel to ensure that AV setup is good

After show (ideally right away but can wait until Monday):

  • Create/submit PR for this repo
    • [ ] Episode directory and README from hackmd
    • [ ] Any other files from the episode that might be useful
    • [ ] Update playlist.md with episode
    • Feel free to self merge
  • [ ] Edit YT description to point to episode directory here
  • [ ] OBS/OS Upgrade if applicable (Never on the day of a show)
jsarkar

comment created time in 3 months

push eventjbeda/dxf2svg

Joe Beda

commit sha d903fc6b5bd1b7a57b7fb4e2fb884f7c1efae529

Update stroke width for how AI sees it Signed-off-by: Joe Beda <joe.github@bedafamily.com>

view details

push time in 3 months

push eventjbeda/dotfiles

Joe Beda

commit sha b217faa7a64c4834d59557a703e324b6afe2e867

Make macos be quiet Signed-off-by: Joe Beda <joe.github@bedafamily.com>

view details

push time in 3 months

pull request commentcncf/toc

Submit k3s for inclusion to CNCF as a sandbox project

The fact that someone has to ask the question implies, to me, that they are confused and see them as overlapping. The closeness of naming implies a connection that isn't there. See also: https://twitter.com/dustinmoris/status/1280886236723503104

cjellick

comment created time in 3 months

pull request commentcncf/toc

Submit k3s for inclusion to CNCF as a sandbox project

FWIW -- I know that this is a spoof account but this tweet shows that there is legitimate confusion over the name k3s.

https://twitter.com/morecobol/status/1280877846567751680

image

cjellick

comment created time in 3 months

more