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.

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)

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

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.

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.

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.

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

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

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

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

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

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

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)

Fixes #240

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

Fixes #240

https://hackmd.io/cNRuv5jvRVuvIbCpbKScMA?view

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)

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

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