Black lives matter.
We stand in solidarity with the Black community.
Racism is unacceptable.
It conflicts with the core values of the Kubernetes project and our community does not tolerate it.
We stand in solidarity with the Black community.
Racism is unacceptable.
It conflicts with the core values of the Kubernetes project and our community does not tolerate it.
Every week the Kubernetes contributing community meet virtually over Google Hangouts. We want anyone who's interested to know what's discussed in this forum.
Agenda:
Notes from meeting:
Auth(n)(z)
Scheduling Policies
…
Zone (un) availability : Resilient to zone failures
Hybrid cloud: some in cloud, some on prem. for various reasons
Avoid cloud provider lock-in. For various reasons
"Cloudbursting" - automatic overflow into the cloud
Location affinity. How close do pods need to be?
Workload coupling
Absolute location (e.g. eu data needs to be in eu)
Cross cluster service discovery
Cross cluster workload migration
Cross cluster scheduling
How do know enough about clusters to know where to schedule
Possibly use a cost function to achieve affinities with minimal complexity
Can also use cost to determine where to schedule (under used clusters are cheaper than over-used clusters)
Cross cluster integration shouldn't create cross-cluster failure modes
Unified visibility
Unified quota and identity management
Botched software upgrades
Botched config upgrades
Botched key distribution
Overload
Failed external dependencies
Where do you draw the "ubernetes" line
Important to not pigeon hole and prevent other users
Satnam - Soak Test