linter run

This commit is contained in:
Nicolai Ort 2024-03-25 13:53:52 +01:00
parent 5ba002ea90
commit b5344f74ca
Signed by: niggl
GPG Key ID: 13AFA55AF62F269F
21 changed files with 25 additions and 29 deletions

View File

@ -27,7 +27,7 @@ The main topic of this talk is: What interface do we choose for what capability.
* Autonomy: external dependency (low) <-> self-service (high) * Autonomy: external dependency (low) <-> self-service (high)
* low: Ticket system -> But sometimes good for getting an expert * low: Ticket system -> But sometimes good for getting an expert
* high: Portal -> Nice, but somethimes we just need a * high: Portal -> Nice, but somethimes we just need a human contact
* Contextual distance: stay in the same tool (low) <-> switch tools (high) * Contextual distance: stay in the same tool (low) <-> switch tools (high)
* low: IDE plugin -> High potential friction if stuff goes wrong/complex (context switch needed) * low: IDE plugin -> High potential friction if stuff goes wrong/complex (context switch needed)
* high: Wiki or ticketing system * high: Wiki or ticketing system

View File

@ -9,13 +9,11 @@ tags:
This talk was by a New York Times software developer. This talk was by a New York Times software developer.
No real value No real value
## Baseline ## Baseline
* How do we build composable components * How do we build composable components
* Workflow of a new service: Create/Onboard -> Develop -> Build/Test/deploy (CI/CD) -> Run (Runtime/Cloud) -> Route (Ingress) * Workflow of a new service: Create/Onboard -> Develop -> Build/Test/deploy (CI/CD) -> Run (Runtime/Cloud) -> Route (Ingress)
## What do we need ## What do we need
* User documentation * User documentation

View File

@ -37,4 +37,4 @@ A podium discussion (somewhat scripted) lead by Pryanka
* Anything else * Anything else
* Jeff: How do we bring our awesome tools (monitoring, logging, security) to the new AI world * Jeff: How do we bring our awesome tools (monitoring, logging, security) to the new AI world
* Paige: Currently many people just use paid apis to abstract the infra, but we need this stuff selfhostable * Paige: Currently many people just use paid apis to abstract the infra, but we need this stuff selfhostable
* Tim: I don'T want to know about the hardware, the whole infra side should be done by the cloudnative teams to let ML-Engi to just be ML-Engi * Tim: I don'T want to know about the hardware, the whole infra side should be done by the cloudnative teams to let ML-Engi to just be ML-Engine

View File

@ -45,7 +45,6 @@ A talk by elastic.
I won't copy the explanations of operators/controllers in this notes I won't copy the explanations of operators/controllers in this notes
{{% /notice %}} {{% /notice %}}
* Many different controllers, including (but not limited to) * Many different controllers, including (but not limited to)
* cluster controler: Register cluster to controller * cluster controler: Register cluster to controller
* Project controller: Schedule user's project to cluster * Project controller: Schedule user's project to cluster

View File

@ -12,7 +12,7 @@ Who have I talked to today, are there any follow-ups or learnings?
## Flux ## Flux
* We talked about automatic helm release updates (lessons learned from flux)[/lessons_learned/02_flux] * We talked about automatic helm release updates [lessons learned from flux](/lessons_learned/02_flux)
## Cloudfoundry/Paketo ## Cloudfoundry/Paketo

View File

@ -47,7 +47,6 @@ flowchart TD
depply-->|Please install|kapp depply-->|Please install|kapp
``` ```
```mermaid ```mermaid
flowchart LR flowchart LR
oa(operator author)-->ba(Bundle and att to catalog) oa(operator author)-->ba(Bundle and att to catalog)