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

BGD-5298 ocean controller v2 migration #214

Merged
merged 1 commit into from
Jun 30, 2024

Conversation

HafdisE
Copy link
Contributor

@HafdisE HafdisE commented Jun 20, 2024

App version of bigdata-operator bumped to the version that has CLUSTER_INFO_MAX_AGE support which allows controlling CM regen frequency. Default value is now 2m which guarantees it gets regenerated each time it is called (call frequency is 3-3.5m)
App version of bigdata-spark-watcher bumped to version that removes some caching of values that no longer need to be cached so that we may properly refresh the cached config values on the fly. Cached credentials are now invalidated every 2m.

This allows for smooth migration to the new ocean controller (v2) and no longer requires you to restart any of the spark services. All you will need to do is install the new controller and scale down the old one.

Jira Ticket

BGD-5298

Demo

Screenshot 2024-06-28 at 09 27 17

Screenshot 2024-06-28 at 09 28 24
Screenshot 2024-06-28 at 09 31 08
Screenshot 2024-06-28 at 09 33 31

Checklist:

  • I have filled relevant self assessment (NodeJS, Frontend, Backend)
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have validated all the requirements in the Jira task were answered
  • I have all neccessary approvals for the design/mini design of this task

HafdisE added a commit that referenced this pull request Jun 26, 2024
* [charts/bigdata-operator] update to 0.4.17, add new var to control cluster info config map invalidation frequency
* [charts/bigdata-spark-watcher] update to 0.5.1, increase frequency of cached credential invalidations
@HafdisE HafdisE force-pushed the BGD-5298-ocean-controller-v2-migration branch from 824a643 to f33a8c3 Compare June 26, 2024 09:18
HafdisE added a commit that referenced this pull request Jun 26, 2024
* [charts/bigdata-operator] update to 0.4.17, add new var to control cluster info config map invalidation frequency
* [charts/bigdata-spark-watcher] update to 0.5.1, increase frequency of cached credential invalidations
@HafdisE HafdisE force-pushed the BGD-5298-ocean-controller-v2-migration branch from f33a8c3 to 6662de4 Compare June 26, 2024 09:37
* [charts/bigdata-operator] update to 0.4.17, add new var to control cluster info config map invalidation frequency
* [charts/bigdata-spark-watcher] update to 0.5.1, increase frequency of cached credential invalidations
@HafdisE HafdisE force-pushed the BGD-5298-ocean-controller-v2-migration branch from 6662de4 to 509043e Compare June 27, 2024 12:34
@HafdisE HafdisE marked this pull request as ready for review June 27, 2024 12:35
@HafdisE HafdisE requested a review from a team as a code owner June 27, 2024 12:35
Copy link
Contributor

@alextarasov-spot alextarasov-spot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
can you provide screenshots, please?

  • the operator deployment template has the expected env var
  • all updated components are running with the expected image version

@HafdisE
Copy link
Contributor Author

HafdisE commented Jun 28, 2024

LGTM can you provide screenshots, please?

  • the operator deployment template has the expected env var
  • all updated components are running with the expected image version

Done :)

@alextarasov-spot alextarasov-spot merged commit 45111d3 into main Jun 30, 2024
1 check passed
@alextarasov-spot alextarasov-spot deleted the BGD-5298-ocean-controller-v2-migration branch June 30, 2024 07:41
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.

2 participants