search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.31k stars 21.5k forks source link

Install in pre-existing namespace #34589

Closed alexcpn closed 5 years ago

alexcpn commented 5 years ago

I tried this and it works perfect. However is it possible to install it on a pre-existing namespace. I want to assign a namespace to a particular node (and its full resources) and want to install the iot edge hub to that particular namespace. This is not working now

helm install --name k8s-edge3 --set "deviceConnectionString=HostName=alexcpn-iot-hub.azure-devices.net;DeviceId=ndac-app-fake;SharedAccessKey=<key>\=" edgek8s/edge-kubernetes --namespace msiot-alexcpn-iot-hub-xx-app-fake Error: release k8s-edge3 failed: namespaces "msiot-alexcpn-iot-hub-xxx-app-fake" already exists

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

DixitArora-MSFT commented 5 years ago

Hi @alexcpn Thank you for your feedback! We will review and provide an update as appropriate.

Alberto-Vega commented 5 years ago

@alexcpn Thanks for reaching out! This question seems better suited for stack-overflow where unlike here there is a community that can help. We have this issues for receiving feedback on improving our docs. Would you please create a post there and share the link to it here?

veyalla commented 5 years ago

@alexcpn Installing into a pre-existing namespace is not yet possible, but we're adding this capability in a future release.

alexcpn commented 5 years ago

Thanks; (is it possible to say what would be the approximate timeline )

veyalla commented 5 years ago

It should be available in the next couple of months for so. Could you please open an issue for this at https://github.com/azure/iotedge/issues as @Alberto-Vega-MSFT suggests so that the engineering team can track it?

alexcpn commented 5 years ago

Done thanks https://github.com/Azure/iotedge/issues/1424

tynevi commented 5 months ago

@alexcpn - A comment in this issue contained an Azure IoT Device Connection String which was flagged in secret scanning. I have replaced it with "key-value" in the comment. We recommend that you revoke existing connection strings and replace with new ones.