-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Rewrite ASM module #1140
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
Rewrite ASM module #1140
Conversation
Thanks for the PR! 🚀 |
e910b17
to
a4d7560
Compare
a4d7560
to
f5b65bd
Compare
995b927
to
7ad8320
Compare
Addressed comments. CI failing on an issue that doesn't seem related to these changes though, any thoughts here? @bharathkkb
|
@Monkeyanator I noticed it when working on another PR. You can switch to using the registry source for |
Opened #1159 since it was affecting a few PRs |
Thanks for looking into it @bharathkkb, made the change from #1159 here but seems like we still run into issues about resources changing (hard to pin down where the step actually fails from the logs). Think the PR with just the fix is failing CI as well |
@Monkeyanator seemed like the failure in #1159 was a flake. I have kicked it off again. Also could we add some kind of upgrade guide for users coming from the old module? Is there a possible upgrade path minimizing disruption? |
@bharathkkb the exposed options and implementation are different enough from the previous implementation where it'll be tough to support a migration path here. Is it possible to document to pin to the old version for this first iteration? Updated the README documenting this. |
Makes sense, I dropped a comment above to move that section to the upgrade guide. |
Super excited that this PR has been merged. Do you think it will solve this issue? #1114 |
Yes, the segfault probably comes from somewhere in the |
Why was asm_version removed? |
The existing ASM module is a near-1:1 wrapper around
install_asm
which is not ideal. This rewritten module uses the ControlPlaneRevision KRM API to provision the control plane. We still break out and use a provisioner to apply the CPR (due to limitations around thekubernetes_manifest
resource) but it's much slimmer than before, and doesn't involve curling down an installation script.