Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't use separate yamls for OC and K8s where possible #99

Open
1 task
sgnn7 opened this issue Jan 31, 2020 · 0 comments
Open
1 task

Don't use separate yamls for OC and K8s where possible #99

sgnn7 opened this issue Jan 31, 2020 · 0 comments
Labels
component/k8s good-first-issue kind/cleanup kind/developer-experience kind/enhancement kind/technical-debt triage/needs-epic triage/scoping

Comments

@sgnn7
Copy link
Contributor

sgnn7 commented Jan 31, 2020

It may be possible (and likely) that yamls can be done with vanilla k8s constructs so that we can get rid of the bifurcated logic in the code.

AC

  • YAMLs are not infra-type specific
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/k8s good-first-issue kind/cleanup kind/developer-experience kind/enhancement kind/technical-debt triage/needs-epic triage/scoping
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sgnn7