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

Make bigdata-crds manages spark-operator crds #254

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

ImpSy
Copy link
Collaborator

@ImpSy ImpSy commented Dec 9, 2024

Jira ticket

https://spotinst.atlassian.net/browse/BGD-6250

Description

https://spotinst.atlassian.net/browse/BGD-6250

Demo

Please add a recording/screenshot of the feature/bug fix in action

Checklist

  • I have added a Jira ticket link
  • I have filled in the test plan
  • I have executed the tests and filled in the test results
  • I have updated/created relevant documentation

How to test

Testing was done on this PR -> https://github.com/spotinst/bigdata-operator/pull/358

Test plan and results

Look into https://github.com/spotinst/bigdata-operator/pull/358 to see the helm upgrade diff works

@ImpSy ImpSy requested a review from a team as a code owner December 9, 2024 16:15
@HafdisE
Copy link
Contributor

HafdisE commented Dec 11, 2024

So we have them in the crds folder for the initial install... and also under templates for installing again on upgrades? Why are the bigdata crds not also following this pattern?

@ImpSy
Copy link
Collaborator Author

ImpSy commented Dec 12, 2024

To ease what is "our" tempates and what comes from "external charts", I decided to copy the spark-operator/crds directory into bigdata-crds/crds and add the new template file in bigdata-crds so we see what we maintain and what comes from "outside"

the crds directory is actually ran after the chart install if the CRD does not already exist
With this new implementation, the "template" CRD will manage install and upgrades

Signed-off-by: ImpSy <3097030+ImpSy@users.noreply.github.com>
@ImpSy ImpSy force-pushed the BGD-6250_bigdata-crds-manage-spark-operator-crds branch from 6cb59ca to cc14500 Compare December 12, 2024 10:20
@ImpSy ImpSy merged commit c90ad92 into main Dec 12, 2024
2 checks passed
@ImpSy ImpSy deleted the BGD-6250_bigdata-crds-manage-spark-operator-crds branch December 12, 2024 13:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants