Deprecation Notice: Upcoming Removal of Specific Blueprints

[vara-bonthu]

Dear Users,

We are planning to deprecate and remove the following blueprints from our repository. This notice is being provided 8 weeks in advance to give you sufficient time to plan your migration or continue using these blueprints if necessary.

Reason for Removal:

One of the key challenges we are currently facing is the ongoing maintenance of these blueprints. Additionally, there has been little to no demand from users or customers for these specific patterns. To optimize our resources and focus on more widely used and requested blueprints, we have decided to deprecate and remove these blueprints.

However, if you believe that one of these patterns is actively used by your customers in production and you would like to see it maintained, please comment on this issue with further details. We value your feedback and are open to reconsideration based on the community's needs.

Please note that customers can still continue to use these blueprints with the existing tag: v1.0.3.

Blueprints to be Deprecated and Removed:

1/ Ray Blueprint:

Action: Removed.
Replacement: The Ray blueprint will be replaced with the JARK stack. The documentation has been updated accordingly.

2/ CDK Folder:

Action: Will be removed.
Details: This folder consisted of the emr-eks and stream-emr-eks blueprints.

• emr-eks-ack: Will be removed.
• emr-eks-fargate: Will be removed.

Further Considerations:

We are also considering the following changes in the near future:

MLFlow Blueprint: potentially removing this blueprint and integrating MLFlow with the JARK stack.
NiFi Blueprint: Considering removal.

Retained and Maintained Blueprint:
emr-eks-karpenter: This is the only EMR on EKS blueprint that will continue to be actively maintained and referred to customers.

Updated Documentation:
The Ray documentation has been updated to point to the JARK stack blueprint.

What You Need to Know:
Action Required: If you are currently using any of the above blueprints in production, you can continue to do so with the existing tag: v1.0.3.

PR Timeline: The PR implementing these changes will be merged after the 8-week notice period.

Thank you for your understanding and cooperation.

[github-actions]

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

[github-actions]

Issue closed due to inactivity.