55 lines
1.7 KiB
Markdown
55 lines
1.7 KiB
Markdown
---
|
|
title: Networking
|
|
weight: 99
|
|
---
|
|
|
|
Who have I talked to today, are there any follow-ups or learnings?
|
|
|
|
## Operator Framework
|
|
|
|
* We talked about the operator lifecycle manager
|
|
* They shared the roadmap and the new release 1.0 will bring support for Operator Bundle loading from any oci source (no more public-registry enforcement)
|
|
|
|
## Flux
|
|
|
|
* We talked about automatic helm release updates (lessons learned from flux)[/lessons_learned/02_flux]
|
|
|
|
## Cloudfoundry/Paketo
|
|
|
|
* We mostly had some smalltalk
|
|
* There will be a cloudfoundry day in Karlsruhe in October, they'd be happy to have us ther
|
|
* The whole KORFI (Cloudfoundry on Kubernetes) Project is still going strong, but no release canidate yet (or in the near future)
|
|
|
|
## Traefik
|
|
|
|
{{% notice style="note" %}}
|
|
They will follow up
|
|
{{% /notice %}}
|
|
|
|
* We mostly talked about traefik hub as an API-portal
|
|
|
|
## Postman
|
|
|
|
* I asked them about their new cloud-only stuff: They will keep their direction
|
|
* The are also planning to work on info materials on why postman SaaS is not a big security risk
|
|
|
|
## Mattermost
|
|
|
|
{{% notice style="note" %}}
|
|
I should follow up
|
|
{{% /notice %}}
|
|
|
|
* I talked about our problems with the mattermost operator and was asked to get back to them with the errors
|
|
* They're currently migrating the mattermost cloud offering to arm - therefor arm support will be coming in the next months
|
|
* The mattermost guy had exactly the same problems with notifications and read/unread using element
|
|
|
|
## Vercel
|
|
|
|
* Nice guys, talked a bit about convincing customers to switch to the edge
|
|
* Also talked about policy validation
|
|
|
|
## Renovate
|
|
|
|
* The paid renovate offering now includes build failure estimation
|
|
* I was told not to buy it after telling the technical guy that we just use build pipelines as MR verification
|