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

#157 finalize v2 spark infrastructure #321

Merged
merged 1 commit into from
Sep 10, 2024

Conversation

cwoods-cpointe
Copy link
Contributor

Default all new applications to use spark-infrastructure to the V2 charts. Mark any V1 users with a depreciation warning. Provide migration instructions for going from V1 -> V2.

Update spark-events to be saved to a more dynamic PVC instead of a S3 bucket.

Signed-off-by: Peter McClonski mcclonski_peter@bah.com

#300 Resolve several issues with the V2 charts

Correct the Spark-event PV host node mount point. Update the spark configmap name to be in line with our documentaion (-conf -> -config).

Corrected a bug in the Configuration-store PVC being writable instead of read only.

@cwoods-cpointe cwoods-cpointe linked an issue Sep 9, 2024 that may be closed by this pull request
10 tasks
|S3 Local | `s3local-deploy-v2` |https://github.com/boozallen/aissemble/blob/{git-tree}/extensions/extensions-helm/aissemble-localstack-chart/README.md[S3 Local,role=external,window=_blank]
|Configuration Store | `configuration-store-deploy-v2` |https://github.com/boozallen/aissemble/blob/{git-tree}/extensions/extensions-helm/aissemble-configuration-store-chart/README.md[Configuration Store,role=external,window=_blank]
|Spark Operator | `aissemble-spark-operator-deploy-v2` |https://github.com/boozallen/aissemble/blob/{git-tree}/extensions/extensions-helm/aissemble-spark-operator-chart/README.md[Spark Operator,role=external,window=_blank]
|Application | Fermenter Profile | ReadMe
Copy link
Contributor Author

Choose a reason for hiding this comment

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

i: Only code format changes

@@ -11,61 +11,61 @@ helm install mlflow oci://ghcr.io/boozallen/aissemble-mlflow-chart --version <AI
# Properties
The following properties are inherited from the base [MLflow chart](https://github.com/bitnami/charts/blob/main/bitnami/mlflow/README.md), but with updated default values.

| Property | Description | Default |
Copy link
Contributor Author

Choose a reason for hiding this comment

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

i: Only code format changes

@@ -21,6 +30,9 @@ sparkApp:
- name: ivy-cache
persistentVolumeClaim:
claimName: ivy-cache
- name: spark-events
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I: Spark events were previously saved to s3. Changed to save to a PVC

Copy link
Contributor

Choose a reason for hiding this comment

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

Should we include this new property in the README properties section?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good question. There is a section on the shared Ivy cache which is similarly a pvc. I can add a section to the readme for Spark-events

@@ -37,17 +37,17 @@ aissemble-spark-operator-chart:
webhook.enable: false
```

| Property | Description | Required Override | Default |
Copy link
Contributor Author

Choose a reason for hiding this comment

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

i: Only code format changes

supplementalVolumeMounts:
- name: configurations
mountPath: "/configurations"
readOnly: true
Copy link
Contributor Author

Choose a reason for hiding this comment

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

i: resolved issue where the configuration-store PVC was not read only

@cwoods-cpointe cwoods-cpointe force-pushed the feature/spark-infrastructure-v2-default branch from 3f6ef81 to a173fd1 Compare September 9, 2024 19:18
Default all new applications to use spark-infrastructure to the V2
charts. Mark any V1 users with a depreciation warning. Provide migration
instructions for going from V1 -> V2.

Update spark-events to be saved to a more dynamic PVC instead of a S3
bucket.

Signed-off-by: Peter McClonski <mcclonski_peter@bah.com>

 #300 Resolve several issues with the V2 charts

Correct the Spark-event PV host node mount point. Update the spark
configmap name to be in line with our documentaion (-conf -> -config).

Corrected a bug in the Configuration-store PVC being writable instead of
read only.
@cwoods-cpointe cwoods-cpointe force-pushed the feature/spark-infrastructure-v2-default branch from 42ec405 to 20ecf37 Compare September 9, 2024 20:56
@cwoods-cpointe cwoods-cpointe merged commit 1ac07a6 into dev Sep 10, 2024
@cwoods-cpointe cwoods-cpointe deleted the feature/spark-infrastructure-v2-default branch September 10, 2024 14:09
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.

Feature: Default spark-infrastructure Helm charts to V2 and ensure migration
4 participants