-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: remove eks-d & eks-a #231
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think a few changes are in order to embrace RKE2 beyond removing EKSD.
Also, we should redeploy the clusters first.
hi @JoeHCQ1 - i could see that point of view, but i wonder if at some point it may make sense to split the mono-bundle into multiple bundles. if so, then some of the naming and folder structure would make that easier. totally could be wrong about that though, and could just flatten things if that makes more sense. i'm OK with holding off on merging this until we replace the EKS-D clusters with RKE2. |
@MxNxPx I'm good with keeping it this way then. I would love to hear sometime what the potential benefits of multiple bundles may be in our context. |
Oh dang it - I forgot we were waiting until we'd redeployed the clusters. Well, that needed done anyway. |
Removing all code that supported building and publishing EKS-D related bundles.