linter run
This commit is contained in:
@@ -37,4 +37,4 @@ A podium discussion (somewhat scripted) lead by Pryanka
|
||||
* Anything else
|
||||
* 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
|
||||
* 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
|
||||
|
||||
@@ -51,4 +51,4 @@ Kevin and Sanjay from NVIDIA
|
||||
|
||||
* There are different KPIs: starvation, prioprity, occupanccy, fainrness
|
||||
* Challenge: What to choose (the multi-dimensional decision problemn)
|
||||
* Needed: A scheduler that can balance the dimensions
|
||||
* Needed: A scheduler that can balance the dimensions
|
||||
|
||||
@@ -22,4 +22,4 @@ Jorge Palma from Microsoft with a quick introduction.
|
||||
* Deployment
|
||||
* Simple CRD that decribes a model, infra and have fun
|
||||
* Creates inferance endpoint
|
||||
* Models are currently 10 (Hugginface, LLMA, etc)
|
||||
* Models are currently 10 (Hugginface, LLMA, etc)
|
||||
|
||||
@@ -16,4 +16,4 @@ It was pretty scripted with prepared (sponsor specific) slides for each question
|
||||
* Smaller LLMs on cpu only is preyy cost efficient
|
||||
* Better scheduling by splitting into storage + cpu (prepare) and gpu (run) nodes to create a just-in-time flow
|
||||
* Software acceleration is cool, but we should use more specialized hardware and models to run on CPUs
|
||||
* We should be flexible regarding hardware, multi-cluster workloads and hybrig (onprem, burst to cloud) workloads
|
||||
* We should be flexible regarding hardware, multi-cluster workloads and hybrig (onprem, burst to cloud) workloads
|
||||
|
||||
@@ -27,9 +27,9 @@ PAtrick Ohly Joined for DRA
|
||||
|
||||
* Kube is the seed for the AI infra plant
|
||||
* Kubeflow users wanted AI registries
|
||||
* LLM on the edge
|
||||
* LLM on the edge
|
||||
* Opentelemetry bring semandtics
|
||||
* All of these tools form a symbiosis between
|
||||
* All of these tools form a symbiosis between
|
||||
* Topics of discussions
|
||||
|
||||
### The working group AI
|
||||
@@ -39,7 +39,7 @@ PAtrick Ohly Joined for DRA
|
||||
* The landscape "cloudnative and ai" is WIP and will be merged into the main CNCF landscape
|
||||
* The future focus will be on security and cost efficiency (with a hint of sustainability)
|
||||
|
||||
### LFAI and CNCF
|
||||
### LFAI and CNCF
|
||||
|
||||
* The direcor of the AI foundation talks abouzt ai and cloudnative
|
||||
* They are looking forward to more colaboraion
|
||||
* They are looking forward to more colaboraion
|
||||
|
||||
@@ -45,7 +45,6 @@ A talk by elastic.
|
||||
I won't copy the explanations of operators/controllers in this notes
|
||||
{{% /notice %}}
|
||||
|
||||
|
||||
* Many different controllers, including (but not limited to)
|
||||
* cluster controler: Register cluster to controller
|
||||
* Project controller: Schedule user's project to cluster
|
||||
@@ -70,7 +69,7 @@ I won't copy the explanations of operators/controllers in this notes
|
||||
* Potential solutions: Replace etcd with the external db
|
||||
* Chosen solution:
|
||||
* The controllers don't use CRDs for storage, but they expose a webapi
|
||||
* Reconciliation still now interacts with the external db and go channels (que) instead
|
||||
* Reconciliation still now interacts with the external db and go channels (que) instead
|
||||
* Then the CRs for the operators get created by the global controller
|
||||
|
||||
### Large scale
|
||||
|
||||
@@ -28,7 +28,7 @@ A talk by Google and Microsoft with the premise of bether auth in k8s.
|
||||
* Gateway Solution:
|
||||
* Gateway TLS secret ref includes a namespace
|
||||
* ReferenceGrant pretty mutch allows referencing from X (Gatway) to Y (Secret)
|
||||
* Limits:
|
||||
* Limits:
|
||||
* Has to be implemented via controllers
|
||||
* The controllers still have readall - they just check if they are supposed to do this
|
||||
|
||||
@@ -85,4 +85,4 @@ A talk by Google and Microsoft with the premise of bether auth in k8s.
|
||||
## Meanwhile
|
||||
|
||||
* Prefer tools that support isolatiobn between controller and dataplane
|
||||
* Disable all non-needed features -> Especially scripting
|
||||
* Disable all non-needed features -> Especially scripting
|
||||
|
||||
@@ -12,7 +12,7 @@ Who have I talked to today, are there any follow-ups or learnings?
|
||||
|
||||
## 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
|
||||
|
||||
|
||||
@@ -8,4 +8,4 @@ Day two is also the official day one of KubeCon (Day one was just CloudNativeCon
|
||||
This is where all of the people joined (over 2000)
|
||||
|
||||
The opening keynotes were a mix of talks and panel discussions.
|
||||
The main topic was - who could have guessed - AI and ML.
|
||||
The main topic was - who could have guessed - AI and ML.
|
||||
|
||||
Reference in New Issue
Block a user