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.

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

Integrate odo with Application and/or Component CRD #1244

Closed
cmoulliard opened this issue Jan 28, 2019 · 1 comment
Closed

Integrate odo with Application and/or Component CRD #1244

cmoulliard opened this issue Jan 28, 2019 · 1 comment
Labels
kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation

Comments

@cmoulliard
Copy link
Contributor

[kind/Feature]

Goal : Integrate odo with the k8s Application and/or Component CRD
why :

  • Reduce development/maintenance costs of odo by delegating responsibilities to maintain k8s resources of an application on the platform using CRD and operator
  • Propose a common approach for all the DevTools to generate resources on the cloud Platform using Application/Component CRD
  • Simplify migration of existing application when images + CVE should be patched, when new or additional features should be installed (e.g istio 1.1, Prometheus, EFK, ...)
  • Delegate complex logic to be part/handled by k8s operator to manage Application status (update) when related resources are created/updated. That will let us to aggregate the status for the different resources created/application or component
  • Support different installation or build strategies : inner, outerloop, knative build/pipelines
@kadel kadel added kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation and removed kind/new feature labels Sep 19, 2019
@girishramnani
Copy link
Contributor

Closing this issue as currently we don't have plans to implement this for next 6 months. Please re-open this if someone feels this is relevant now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation
Projects
None yet
Development

No branches or pull requests

3 participants