BGD-5298 ocean controller v2 migration #214
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Checklist: