Managed updates scaling #37
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.
Renamed the Indexer CR to IndexerCluster and SearchHead CR to SearchHeadCluster
Added support for fully managed updates and scaling of the IndexerCluster and SearchHeadCluster resources. The operator now interacts with Splunk Enterprise's REST apis to manage cluster membership, decommissioning, quarantine, etc. as necessary.
The status fields for all CRDs are now actively managed by the operator, and some have been added as print lines so that more information is shown when you run for example
kubectl get searchhead
:The kubectl scale command should not work with all CRs (except for LicenseMaster, since there is only 1)
Renamed environment variables SPLUNK_IMAGE to RELATED_IMAGE_SPLUNK_ENTERPRISE and SPARK_IMAGE to RELATED_IMAGE_SPLUNK_SPARK (for Red Hat certification)
Updated default volume claims for etc and var to 10Gi and 100Gi, respectively
Fixed naming of splunk.reconcile package