-
Notifications
You must be signed in to change notification settings - Fork 28
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
scylla_install_image: disable cloud provider agents #627
Conversation
currently if BYOA customer will assigned required AWS Profile on instance or will deploy scylla in GCP customer will able to fetch metadata about the OS itself, and also will able to execute command on a target instance, which may leads to loose of control for instances deployed in BYOA. Fixes: scylladb/scylla-pkg#4883
elif args.target_cloud == 'azure': | ||
kernel_opt = ' rootdelay=300' | ||
grub_variable = 'GRUB_CMDLINE_LINUX' | ||
run('systemctl mask walinuxagent', shell=True, check=True) |
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.
Aren't we using this for something in SCT ?
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.
yes, we use it for rebooting with running OS command (reboot -f
) due issue with SDK (scylladb/scylla-cluster-tests#6628)
We would need to adjust SCT to enable it back when VM is provisioned.
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.
@soyacz Can you open an issue or send a fix? we should probably also have it for 2025.1 since this is about to be backported
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.
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.
Thanks @soyacz , I assume we can move forward with this PR then ?
Linux agent on Scylla instances on Azure is disabled by default. scylladb/scylla-machine-image#627 Add cloud init script that enables it back for testing purposes.
Linux agent on Scylla instances on Azure is disabled by default. scylladb/scylla-machine-image#627 Add cloud init script that enables it back for testing purposes.
Linux agent on Scylla instances on Azure is disabled by default. scylladb/scylla-machine-image#627 Add cloud init script that enables it back for testing purposes.
Linux agent on Scylla instances on Azure is disabled by default. scylladb/scylla-machine-image#627 Add cloud init script that enables it back for testing purposes.
Linux agent on Scylla instances on Azure is disabled by default. scylladb/scylla-machine-image#627 Add cloud init script that enables it back for testing purposes. (cherry picked from commit 6f24ccb)
Linux agent on Scylla instances on Azure is disabled by default. scylladb/scylla-machine-image#627 Add cloud init script that enables it back for testing purposes. (cherry picked from commit 6f24ccb)
currently, if the BYOA customer is assigned the required AWS Profile on the instance or will deploy scylla in GCP customer will able to fetch metadata about the OS itself, and also be able to execute a command on a target instance, which may lead to loose of control for instances deployed in BYOA.
Fixes: https://github.com/scylladb/scylla-pkg/issues/4883
Testing