Skip to content
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.

reduce k8s upgrade merge conflicts: RFC 141: Go investigation #10943

Closed
slimsag opened this issue May 22, 2020 · 3 comments
Closed

reduce k8s upgrade merge conflicts: RFC 141: Go investigation #10943

slimsag opened this issue May 22, 2020 · 3 comments
Assignees
Labels
estimate/3d RFC-141 spike Time boxed investigation meant to facilitate more granular planning.

Comments

@slimsag
Copy link
Member

slimsag commented May 22, 2020

Similar to:

I think it makes sense for us to consider something like what sourcegraph-server-gen was in the past, but in the form of:

src k8s config.yaml -> generates deploy-sourcegraph/base but with modifications

I'm not saying we need to do this in 3.17, currently, just that I think considering this alongside Cue and Dhall makes sense. Thoughts @ggilmore?

@slimsag slimsag added RFC-141 team/distribution spike Time boxed investigation meant to facilitate more granular planning. estimate/3d labels May 22, 2020
@slimsag slimsag added this to the Backlog milestone May 22, 2020
@ggilmore
Copy link
Contributor

ggilmore commented May 23, 2020

@slimsag I think this is a valid alternative for us to explore. I won't have time in 3.17 to look into this however (unless we have some a priori reasoning that Cue or Dhall won't meet our needs)

@ggilmore
Copy link
Contributor

This might also take longer than the three day estimate since we'd developing this system from scratch

@slimsag slimsag changed the title spike: RFC 141 Implementation Round 2: Go RFC 141: spike: Implementation Round 2: Go Jun 3, 2020
@slimsag slimsag changed the title RFC 141: spike: Implementation Round 2: Go RFC 141: reduce k8s upgrade merge conflicts: Go investigation Jun 23, 2020
@slimsag slimsag changed the title RFC 141: reduce k8s upgrade merge conflicts: Go investigation reduce k8s upgrade merge conflicts: RFC 141: Go investigation Jun 23, 2020
@slimsag slimsag modified the milestones: Backlog, 3.18 Jul 1, 2020
@slimsag
Copy link
Member Author

slimsag commented Aug 24, 2020

From what I understand we no longer plan on investigating this route, closing.

@slimsag slimsag closed this as completed Aug 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
estimate/3d RFC-141 spike Time boxed investigation meant to facilitate more granular planning.
Projects
None yet
Development

No branches or pull requests

2 participants