GoogleContainerTools/skaffold

Try downgrading config when unknown (too new) version

Open

#6,184 opened on Jul 11, 2021

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Go (1,416 forks)batch import
bugbash/q4-2022help wantedkind/usabilitymeta/examplesmeta/release

Repository metrics

Stars
 (12,822 stars)
PR merge metrics
 (PR metrics pending)

Description

Cloud Shell users who try our examples hit unknown api version errors for several days after our release as Cloud Shell’s Skaffold installation lags. This isn’t a great experience.

Here are three approaches:

  1. What if we tried reloading the config but using our latest known confit? Chances are that most configs will load just fine.
  2. What if we stop updating the apiVersion in the examples except when required for new fields it changes?
  3. What if we updated the example apiVersions as a separate step once the new version of Shahid has prepared to Cloud Shell and gcloud?

Contributor guide

Research direction
Look at how Skaffold loads its config and handles apiVersion. Identify where the 'unknown api version' error is raised. Then implement a fallback mechanism to try the latest known config version.
Tech stack
gokubernetes
Domain
devops
Issue type
Bug
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-3 hours
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
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75