Releases: GlueOps/k3d
Releases · GlueOps/k3d
v0.3.2
What's Changed
Enhancements 🎉
- feat: adding registry.k8s.io by @venkatamutyala in #36
- feat: enabling k3s service logs by @venkatamutyala in #40
Other 🐛
- chore(deps): update rancher/k3s docker tag to v1.28.14 by @glueops-svc-account in #22
- chore(deps): update rancher/k3s docker tag to v1.29.10 by @public-glueops-renovatebot in #30
- chore(deps): update rancher/k3s docker tag to v1.29.11 by @public-glueops-renovatebot in #34
- chore(deps): update rancher/k3s docker tag to v1.30.8 by @public-glueops-renovatebot in #31
- chore(deps): update rancher/k3s docker tag to v1.30.9 by @public-glueops-renovatebot in #38
- chore(deps): update rancher/k3s docker tag to v1.30.10 by @public-glueops-renovatebot in #39
- chore(deps): update rancher/k3s docker tag to v1.30.11 by @public-glueops-renovatebot in #41
New Contributors
- @glueops-svc-account made their first contribution in #27
- @public-glueops-renovatebot made their first contribution in #30
Full Changelog: v0.3.1...v0.3.2
v0.3.1
v0.3.0
What's Changed
Enhancements 🎉
- feat: adding another node for glueops platform. Specifically for argocd-application-controller by @venkatamutyala in #8
- feat: migrating to tailscale based registry and planning to delete th… by @venkatamutyala in #11
Other 🐛
- chore(deps): update rancher/k3s docker tag to v1.28.10 by @renovate in #10
- fix: domain for registry by @venkatamutyala in #12
- chore(deps): update rancher/k3s docker tag to v1.28.11 by @renovate in #15
- chore(deps): update rancher/k3s docker tag to v1.28.12 by @renovate in #16
- docs(readme): update docs to reflect new username by @fernandoataoldotcom in #19
New Contributors
Full Changelog: v0.2.0...v0.3.0
v0.2.0
What's Changed
Enhancements 🎉
- feat: setting k8s version explicitly to 1.28.X by @venkatamutyala in #6
- Feature/configure node machine by @fernandoataoldotcom in #7
New Contributors
- @fernandoataoldotcom made their first contribution in #7
Full Changelog: 0.1.0...v0.2.0
v0.1.0
feat: added public registry pull through cache to avoid rate limits @venkatamutyala (#2)
This is using a VM we have in hetzner. All of our static dev environments have been whitelisted. Codespaces + anything that is ephemeral needs to be whitelisted manually here:
https://console.hetzner.cloud/projects
We get 20TB of monthly transfer with hetzner for free so we may want to consider just keeping it publicly accessible
Deployed here:
https://github.com/GlueOps/docker-compose-container-registry-pull-through-caches