-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Add support for Azure Resource Manager (ARM) #19146
Comments
Looks like we should do it. @dadoonet is there anything to discuss here (it has the |
@dadoonet It seems that you already started working on it. Is there a planned date for release? |
No date sorry. I just can tell that this will happen only with 5.0 series or later. So won't be available for 2.x series. |
We would like to contribute, can you publish the branch that you are working on,so we may continue with that? |
Will this support using an Azure Scale Sets to discover member nodes? |
Hello, any update on this piece of work? Or at least a placeholder plugin for the "azure-discovery-arm" plugin? |
+1 for this plugin |
Supported settings so far: ```yml cloud: azure-arm: client_id: FILL_WITH_YOUR_CLIENT_ID secret: FILL_WITH_YOUR_SECRET tenant_id: FILL_WITH_YOUR_TENANT subscription_id: FILL_WITH_YOUR_SUBSCRIPTION_ID discovery: zen.hosts_provider: azure-arm azure-arm: host: type: private_ip name: azure-esnode-master-* group_name: azure-preprod region: westeurope refresh_interval: 10s ``` Closes elastic#19146
Supported settings so far: ```yml cloud: azure-arm: client_id: FILL_WITH_YOUR_CLIENT_ID secret: FILL_WITH_YOUR_SECRET tenant_id: FILL_WITH_YOUR_TENANT subscription_id: FILL_WITH_YOUR_SUBSCRIPTION_ID discovery: zen.hosts_provider: azure-arm azure-arm: host: type: private_ip name: azure-esnode-master-* group_name: azure-preprod region: westeurope refresh_interval: 10s ``` Closes elastic#19146
@dadoonet what is the status of this? was this released and can be used with 5.x? Classic plugin has a deprecated warning but no ARM plugin seems to be available at this point? |
@synhershko I made some progress recently on this at #22679. In the meantime, if you want to use azure discovery you still need to use the classic version of the plugin even though it's deprecated. |
Problem is its useless if you use ARM for your deployment. Any chance this
can be backported (and finished soon :) ) ?
…On Jun 7, 2017 3:26 PM, "David Pilato" ***@***.***> wrote:
@synhershko <https://github.com/synhershko> I made some progress recently
on this at #22679 <#22679>.
Not ready yet. My plan is to have something ready for 6.x series.
In the meantime, if you want to use azure discovery you still need to use
the classic version of the plugin even though it's deprecated.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#19146 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAM9HNhhxMdrPxzyv9SdxFT8tYEgF14Uks5sBpb-gaJpZM4JBA0C>
.
|
I don't think it will be ever backported when finished. |
We had an internal discussion on this and, while generally useful, think that we currently cannot take this one on, in particular give it the proper testing, support and maintenance that we provide for the other plugins in the ES repo. This might be a better fit as a community plugin for now. As a clear indication that we're not going to work on this in the foreseeable future, I'm closing this issue. |
As explained in #19144 we could create a new plugin named
discovery-azure-arm
which is based on the newest versions of the Azure SDK.Classic was based on private key / password which was bad for what we want to achieve with such a plugin.
ARM uses now key / secrets which are really much more flexible and safer.
Basically you can now write code like this example:
The text was updated successfully, but these errors were encountered: