# Spegel Community Meeting

Learn more about the community meeting on our [community page](https://spegel.dev/project/community/).

## 2025-06-03

### Atendees

* Philip Laine
* Sheriffo Ceesay
* Volodymyr Koshkarov
* Junaid Chaudry

### Agenda

* Feature enhancement: Allow `resolveTags: upstreamFirst`, to first check upstream for tag resolution, but if fails, use spegel.
* https://github.com/spegel-org/spegel/issues/859

### Notes

## 2025-05-27

### Atendees

* Philip Laine

### Agenda

* Release schedule.

## 2025-05-20

### Atendees

* Philip Laine
* Sheriffo Ceesay

### Agenda

* OCI refactoring and content events.

### Notes

## 2025-05-06

### Atendees

* Philip Laine
* Sheriffo Ceesay

### Agenda

### Notes

## 2025-04-29

### Atendees

* Philip Laine
* Sheriffo Ceesay

### Agenda

* v0.2.0 Release

### Notes

* Initial benchmarking of large images looks promicing, but still open questions about how things work with limited bandwidth.

## 2025-04-22

### Atendees

* Philip Laine
* Roberth Strand
* Simon Gottschlag

### Agenda

### Notes

No specific agenda topics were dicsussed, mostly general thoughts about Spegel.

## 2025-04-15

### Atendees

* Philip Laine
* Sheriffo
* JP Philips

### Agenda

* Topology aware routing feature update.
* Removing node taints when Spegel is deployed.
* https://github.com/spegel-org/spegel/pull/707
* Remove resolve self check and disable fallback registry by default.
* Share specific problem related to my benchmark pipeline (httpReadSeeker).

### Notes

* During benchmarking of image pulls through images (1GB to 30GB) flaky errors related to http read seek errors.
* Explore further simplifying the uninstall process by offering a separate chart to do this on all nodes.
* Sheriffo will create a issue sharing logs to help reproducing the error.
* There may be a need to create a SystemD deployment mechanism for Spegel to enable node local deployment.

## 2025-04-08

### Atendees

* Philip Laine
* Volodymyr Koshkarov
* JP Philips

### Agenda
- Kubecon updates!
- Successful happy-path testing on GKE GCP.
- Thundering Herd load testing.
- Status of requested features.

### Notes

* JP is looking at doing a POC with Spegel at Netflix.
* Happy path testing with Spegel shows that it is faster than Dragonfly.
* Thundering heard problem causes issues when multiple clients are hitting the same instance.
* Need some sort of solution to backoff in these kinds of scenarios.
* Some concerns were raised about the long term future of Spegel as it is a project run by a single maintainer. This is a valid point that we don't really have a solution of right now as the amount of contributions from third parties is low.

## 2025-04-01

**Cancelled due to KubeCon EU**

## 2025-03-25

### Atendees

* Philip Laine
* Volodymyr Koshkarov
* Sheriffo Ceesay

### Agenda

### Notes

* Vlad is going to test Spegel on EKS to validate functionaility.
* Dragonfly seems to be to complicated to setup which is pusing a lot of users to Spegel.
* Should consider writing a blog post comparing Spegel to Drangonfly.
* Lazy loading verification is a useful feature to be used together with Spegel. Verifying and documentign compatibility would be helpful.
* Network topology awaremness would be a huge cost saver for larger users. Also would improve performance.
* Airgap cluster when network connection or registry goest down is very useful.

## 2025-03-18

### Atendees

* Philip Laine
* Sheriffo Ceesay

### Agenda

### Notes

* Sheriffo has been benchmarking Spegel to see how it could be used at Huawei. Initial testing shows pull time or a 30GB image from upstream is around 11 minutes while from Spegel is 6 minutes. This still does not solve the initial pull problem before images can be pulled from Spegel.
* There are many avenues to explore performance improvements that could increase speed when pulling large images.

## 2025-03-04

### Atendees

* Philip Laine

### Agenda

### Notes

## 2025-02-25

### Atendees

* Philip Laine

### Agenda

### Notes