GoogleContainerTools/skaffold

[FR] Redeploy resources that get changed.

Open

#5,540 opened on Mar 12, 2021

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Go (1,416 forks)batch import
area/deployhelp wantedkind/feature-requestpriority/p3

Repository metrics

Stars
 (12,822 stars)
PR merge metrics
 (Avg merge 3d 6h) (16 merged PRs in 30d)

Description

I was following up this stackoverflow thead https://stackoverflow.com/questions/66601242/development-lifecycle-for-fast-starting-pods-with-dependency-on-slow-starting-p

Skaffold right now redeploys the whole application when we detect changes. It would be worth looking into limiting this to redeploy on the affected resources or mark some resources as static and not under development

Contributor guide

Research direction
Investigate how Skaffold currently handles change detection and redeployment. Then design a mechanism to identify which resources were affected by a change and redeploy only those, or allow marking resources as static. Focus on the deployer logic and resource graph.
Tech stack
go
Domain
devopsinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetesSkaffold
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50