Skip to content
This repository has been archived by the owner on Oct 22, 2021. It is now read-only.

Use the Eirini helm chart instead of the BOSH release #47

Closed
viovanov opened this issue Oct 8, 2019 · 4 comments
Closed

Use the Eirini helm chart instead of the BOSH release #47

viovanov opened this issue Oct 8, 2019 · 4 comments
Labels
Priority: Medium Status: Not Implemented This issue will not be implemented due to reasons that should be listed on issue conversation thread Type: Enhancement New feature or request
Projects

Comments

@viovanov
Copy link
Member

viovanov commented Oct 8, 2019

Is your feature request related to a problem? Please describe.
We'd like to use Kubernetes-native components where available.

Describe the solution you'd like
Instead of converting the Eirini BOSH release through the CF Operator, use its helm chart.

What is the impact?
We wouldn't need to support the Eirini BOSH release anymore.

How to measure it?
Everything should work as before.

@viovanov viovanov transferred this issue from SUSE/scf Oct 18, 2019
@viovanov viovanov added this to Icebox in kubecf Oct 18, 2019
@c0d1ngm0nk3y
Copy link
Contributor

We have done the same as a "spike" and you can find the result here: https://github.com/akhinos/kubecf-external-eirini. There is a README.md with the changes we had to apply to make it work.

  • Changes to kubecf, e.g. install bits but not eirini
  • Changes to the eirini-release, e.g. make registry_address and registry_port configurable via helm
  • Usage of shalm (https://github.com/kramerul/shalm) to install the helm charts (cf-operator, kubecf, eirini) to address dependencies, e.g. timing, secrets that have to be "smuggled", ...

@stale
Copy link

stale bot commented Feb 4, 2020

This issue has been automatically marked as stale because it has not had recent activity. If this issue is still relevant then let us know how to help move it forward. Thank you for your contributions.

@stale stale bot added the Type: Stale Issues inactive for a period of time label Feb 4, 2020
@f0rmiga f0rmiga moved this from Icebox 🍦 to Under review 🙇🏻‍♀️ in kubecf Feb 18, 2020
@f0rmiga f0rmiga moved this from Under review 🙇🏻‍♀️ to In progress ⏳ in kubecf Feb 18, 2020
@f0rmiga
Copy link
Member

f0rmiga commented Feb 18, 2020

@HeavyWombat is working on this.

@stale stale bot removed the Type: Stale Issues inactive for a period of time label Feb 18, 2020
@fargozhu fargozhu added this to the 1.1.0 milestone Mar 9, 2020
@fargozhu fargozhu moved this from In progress ⏳ to To Do 🔜 in kubecf Mar 12, 2020
@fargozhu fargozhu modified the milestones: 1.1.0, 1.2.0 Mar 12, 2020
@fargozhu fargozhu linked a pull request Mar 16, 2020 that will close this issue
7 tasks
@fargozhu fargozhu added Status: Blocked Dependencies on other issues and/or pull requests and removed Status: WIP labels Mar 16, 2020
@f0rmiga f0rmiga moved this from To Do 🔜 to In progress ⏳ in kubecf Mar 17, 2020
@fargozhu fargozhu moved this from In progress ⏳ to To Do 🔜 in kubecf Mar 19, 2020
@fargozhu fargozhu modified the milestone: Next Release Mar 19, 2020
@viovanov
Copy link
Member Author

#477 deals with this

kubecf automation moved this from To Do 🔜 to Done 🚀 Mar 26, 2020
@fargozhu fargozhu added Status: Not Implemented This issue will not be implemented due to reasons that should be listed on issue conversation thread and removed Status: Blocked Dependencies on other issues and/or pull requests labels Apr 16, 2020
@fargozhu fargozhu removed this from the Next Release milestone Apr 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Priority: Medium Status: Not Implemented This issue will not be implemented due to reasons that should be listed on issue conversation thread Type: Enhancement New feature or request
Projects
kubecf
  
Done 🚀
Development

Successfully merging a pull request may close this issue.

5 participants