You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
Using the DO provisioner, a virtual machine is created successfully, however the Gargantua-Shell cannot access the VM as a firewall rule for SSH ingress (port 22) has not been created and attached to the VM.
What you expected to happen:
When the VM is provisioned, the correct ingress is created and attached to the VM to allow Shell access via the UI.
How to reproduce it (as minimally and precisely as possible):
Install the hf-provisioner-digitalocean provisioner via Helm.
Set a secret with the key/value pair of token: <yourDigitalOceanToken>
Update the environment to use the hobbyfarm.io/provisioner: digitalocean annotation.
Update the environment to use spec.provider: digitalocean.
Set the environmental_specifics to use the DO region and token-secret.
Update the template_mapping to set the image, size, and ssh_username: root.
Anything else we need to know?:
The VM deploys as expected, just doesn't have ingress.
Environment:
hf-provisioner-digitalocean version: v0.0.1
The text was updated successfully, but these errors were encountered:
What happened:
Using the DO provisioner, a virtual machine is created successfully, however the Gargantua-Shell cannot access the VM as a firewall rule for SSH ingress (port 22) has not been created and attached to the VM.
What you expected to happen:
When the VM is provisioned, the correct ingress is created and attached to the VM to allow Shell access via the UI.
How to reproduce it (as minimally and precisely as possible):
hf-provisioner-digitalocean
provisioner via Helm.token: <yourDigitalOceanToken>
hobbyfarm.io/provisioner: digitalocean
annotation.spec.provider: digitalocean
.region
andtoken-secret
.image
,size
, andssh_username: root
.Anything else we need to know?:
The VM deploys as expected, just doesn't have ingress.
Environment:
The text was updated successfully, but these errors were encountered: