For support using your Leafcloud account or questions regarding availability, you can contact Leafcloud by email at [your_company_name].support@leaf.cloud or hello@leaf.cloud
Additionally, you can call +31(0)202443794 during business hours (GMT+1)
For support using your Leafcloud account or questions regarding availability, you can contact Leafcloud by email at [your_company_name].support@leaf.cloud or hello@leaf.cloud
Additionally, you can call +31(0)202443794 during business hours (GMT+1)
If your authorization link has expired, please send an email to [your_company_name].support@leaf.cloud requesting a new authorization link.
You receive €100 in free credits upon creating your Leafcloud account. Any of these credits that remain unspent last for 15 days.
The €100 in free credits you receive upon creation of your account cannot be used for Leafcloud GPUs
Your free trial period lasts for 15 days after you have created your account, or once your €100 in free credit has been spent.
After your free trial period has expired, you will be billed for the use of Leafcloud services in accordance with our pricing model. For more information about the various costs of our services, visit our Pricing page
Yes, to create a Leafcloud account, you must fill in your credit card details as requested in the sign-up form. Leafcloud will not bill you until your free credits have been used up or have expired. For more information about the various costs of our services, visit our Pricing page.
Yes, all prices listed on our website exclude VAT. For VAT-included pricing, please get in touch with us directly.
At Leafcloud we do our best to make sure your cloud environment is safe and secure. For this reason, we block all outgoing SMTP (E-mail) originating from customers by default. This helps us fight people sending SPAM from our network, and prevents your e-mails from being blocked by blacklists.
What does this mean for you?
For most customers, this has no effect. But if you have a service configured to automatically send e-mail, for example, to reset a password from your site, or send notifications you may see that these e-mails are not delivered.
What if you need to send e-mail from your server?
If you have a need to send an e-mail from your server you typically don't need to send e-mail directly to the recipient. Services such as SendGrid and Mailjet offer relay services with authentication on open port numbers that offer a solution for this problem. They have free tiers that typically suffice for such use-cases.
If you prefer direct e-mail delivery we can also make an exception for you in our firewall. Please get in touch through support, and we'll be happy to set that up for you.
To get a forecast of your next monthly bill you can check your ‘rating’ on the Leafcloud cloud control panel. Prices listed are in Euro’s and before any discounts.
Yes, you can request a copy of your invoice by sending an email to [your_company_name].support@leaf.cloud
Most likely, you have not fully removed one or more of your active services. You can check if this is the case by logging in to your dashboard and check for any active services such as: volumes, instances, floating IPs, load balancers, or storage. If you do not have any visible active services, please contact support through [your_company_name].support@leaf.cloud
To make sure you do not receive invoices for Leafcloud services, please make sure you have no more active services such as volumes, instances, floating IPs, load balancers, or storage visible on your dashboard. If you do not have any visible active services, please contact support through [your_company_name].support@leaf.cloud
If you wish your Leafcloud account deleted, please send an email request to [your_company_name].support@leaf.cloud and provide us with the following information (you must be an Administrator of a project to request deletion of a project):
Please note that this process is permanent and, as such, cannot be undone. Conforming to GDPR, we will no longer have your personal information on file. Please note that replying to your confirmation email will generate a new personal information record. Deletion of data does not extend to prior billing information, which is stored in accordance with our legal requirements.
You can add members to your team by following these steps:
Please have the administrator of your project send a request to [your_company_name].support@leaf.cloud and provide us with the following information:
Please note that this process can take up to 72 hours (about three days) to be verified and processed.
Yes, upgraded or expanded quotas are available on request. If you need your quota expanded, you can contact us at hello@leaf.cloud.
Yes, you can extend the disk space of an instance that is already running.
The safest and most flexible way to do this requires multiple Volumes and a bit of planning.
Follow the steps below. You can find step-by-step guides to various sections here, in our documentation.
vgcreate /dev/MyVG01 /dev/vdb
lvcreate -L +9G --name test MyVG01
mkfs -t ext4 /dev/MyVG01/test
mkdir /mnt/test; mount -rw /dev/MyVG01/test /mnt/test
vgextend /dev/MyVG01 /dev/vdc
lvextend -L +11G /dev/MyVG01/test
resize2fs /dev/MyVG01/test
Alternatively, you can use a quicker and riskier approach. It is possible to apply something akin to:
OS_VOLUME_API_VERSION=3.42 cinder extend <volume_id><SIZE_IN GB>see: https://docs.leaf.cloud/en/latest/volumes/Extending-a-bootable-volume.html
However, this solution runs the risk of causing data loss and is not recommended.
If your Volume is stuck in 'reserved' state please send an email to [your_company_name].support@leaf.cloud
Yes, you can use Let's Encrypt with a Kubernetes load balancer by using ingress-nginex in combination with certbot certmanager as described below.
First, run:
~~~
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.45.0/deploy/static/provider/cloud/deploy.yaml
~~~
This will create a new namespace called ingress-nginex, inside which the nginex controller is deployed.
Next, run:
~~~
---
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
name: <your-project>-ingress
namespace: <your-project>
annotations:
cert-manager.io/issuer: "letsencrypt-prod"
kubernetes.io/ingress.class: "nginx"
spec:
tls:
- hosts:
- join.leaf.cloud
secretName: <your-project>-ingress-tls
rules:
- host: join.leaf.cloud
http:
paths:
- path: /
pathType: Prefix
backend:
serviceName: <your-project>-entrypoint
servicePort: 8000
---
apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
namespace: <your-project>
name: letsencrypt-prod
spec:
acme:
server: https://acme-v02.api.letsencrypt.org/directory
email: my@email.com
privateKeySecretRef:
name: letsencrypt-prod
solvers:
- http01:
ingress:
class: nginx
~~~
First, enter the following:
~~~
openstack coe cluster config my-k8s-cluster
export KUBECONFIG=/home/<username>/config
~~~
Now, kubectl should have access to your Kubernetes cluster. To validate this, enter:
~~~
kubectl get nodes -o wide
~~~
This should list the pods that your Kubernetes cluster is running.
Check [here](https://docs.leaf.cloud/en/latest/kubernetes/creating-a-kubernetes-cluster.html#create-a-cluster) for more information.
###
Yes, you can do this by configuring Leafcloud S3 compatible Object Storage in pgo.yml. To do this, follow the steps below:
**Step 1: create credentials for the ec2 compatible Leafcloud API**
First, you need to create credentials for the ec2 compatible Leafcloud API:
~~~
openstack ec2 credentials create
+---------------------+----------------------------------+
| Field | Value |
+---------------------+----------------------------------+
| default_project_id | 17e5a06a7ce34sjfu5b6e0eejt00663c |
| domain_id | default |
| enabled | True |
| id | d407b0kckdu3994j5jjg8403c0973cf9 |
| name | myuser |
| options | {} |
| password_expires_at | None |
+---------------------+----------------------------------+
~~~
~~~
Cluster:
BackrestS3Bucket: my-postgresql-backups-example
BackrestS3Endpoint: leafcloud.store
BackrestS3Region: europe-nl-ams1
BackrestS3URIStyle: host
BackrestS3VerifyTLS: true
~~~
Click [here ](https://access.crunchydata.com/documentation/postgres-operator/4.7.2/architecture/disaster-recovery/#using-s3)for more information.
**Step 2: Schedule your backups**
Second, schedule your backups as follows:
~~~
pgo create schedule hacluster --schedule="0 1 * * *" \
--schedule-type=pgbackrest --pgbackrest-backup-type=full
pgo create schedule hacluster --schedule="0 */3 * * *" \
--schedule-type=pgbackrest --pgbackrest-backup-type=incr
~~~
Click [here](https://access.crunchydata.com/documentation/postgres-operator/4.7.2/pgo-client/common-tasks/#disaster-recovery-backups-restores) for more information.
The autohealer will replace instances that become unreactive, for example, because they run out of memory.
you can disable it by entering the following:
~~~
kubectl -n kube-system patch daemonset magnum-auto-healer -p '{"spec": {"template": {"spec": {"nodeSelector": {"non-existing": "true"}}}}}'
~~~
You can disable your cluster autoscaler as follows:
~~~
kubectl -n kube-system scale deployment cluster-autoscaler --replicas=0
~~~
the user that you would probably need is:
~~~
core
~~~
To get it, enter the following command:
~~~
ssh -I ~/.ssh/id_rsa core@45.135.56.227
~~~