# Gcore Edge Cloud > Gcore Cloud is an IaaS and PaaS platform providing on-demand compute, storage, networking, containers, databases, and managed services across more than 30 global regions. - [Cloud](https://docs.gcore.com/cloud.md): Gcore Cloud is an IaaS and PaaS platform providing on-demand compute, storage, networking, containers, databases, and managed services across more than 30 global regions. - [Bandwidth and traffic](https://docs.gcore.com/cloud/bandwidth-and-traffic.md): Configure bandwidth limits and monitor network traffic for Gcore compute resources - Basic VMs support up to 200 Mbps, Cloud Virtual Instances up to 1 Gbps, Network optimised VMs up to 10 Gbps, and Bare Metal servers 10 Gbps or higher, with free unlimited VM ingress and egress. - [Billing](https://docs.gcore.com/cloud/billing.md): Configure PAYG billing for Edge Cloud resources charged per minute; manage balance top-ups, payment methods, and service suspension thresholds; track separate charges for Virtual Machines, Volumes, IP addresses (floating, virtual, reserved), snapshots, images, Windows licenses, Bare Metal servers, AI GPUs/IPUs, Managed Logging storage volume, and Function as a Service compute usage. ## Getting started - [Manage resource quotas](https://docs.gcore.com/cloud/getting-started/request-a-quota-increase.md): Check current quota limits and usage for Cloud resources by region, and request quota increases via the Customer Portal Quotas Viewer or the Gcore REST API using Python SDK, Go SDK, or curl. ## Projects - [Create and manage projects](https://docs.gcore.com/cloud/getting-started/projects/create-a-project.md): Create and manage Edge Cloud projects as isolated resource containers via Gcore Customer Portal or REST API or Terraform. ## Users - [User roles and rights](https://docs.gcore.com/cloud/getting-started/projects/users/user-roles-and-rights.md): User roles and permissions in Gcore Cloud - Client Administrator, Project Administrator, Project User, Project Internal Network Only User, and Project Observer control access to Virtual Machines, Bare Metal, Volumes, File Shares, GPU Cloud, Managed Kubernetes, Function as a Service, Container as a Service, Managed Logging, Networks, Firewalls, Load Balancers, and audit logs. - [Add users to a project](https://docs.gcore.com/cloud/getting-started/projects/users/add-a-new-user-to-your-project.md): Invite users to a project via Project Settings, Access tab; enter an email address and select a role to send an invitation to new or existing users. - [Manage user access](https://docs.gcore.com/cloud/getting-started/projects/users/manage-user-access-to-your-project.md): Manage project user access via Project Settings, Access tab; edit roles, deny access with Delete role, or restore access by reassigning a role. - [View user actions](https://docs.gcore.com/cloud/getting-started/projects/users/view-user-actions.md): View user action logs in the Gcore Customer Portal via Cloud Management > User Actions; filter by resource name, project, regions, action type, and resource type, or by a custom time range. - [Cost reports](https://docs.gcore.com/cloud/getting-started/view-statistics-on-expenses.md): View Cloud resource usage and costs via Cost Report (Pay-As-You-Go rates) or Reservation Cost Report (with resource commitment discounts), filtered by Project, Region, Resource type, and consumption period, accessible through portal and Cost Reports API. ## Resource reservation - [About resource reservation](https://docs.gcore.com/cloud/getting-started/resource-reservation/about-resource-reservation.md): Create long-term resource reservations for Gcore Cloud servers with 1-year or 3-year terms at discounted rates, selecting region, server type, Windows License option, quantity, and reservation period via the Reservations portal. ## Virtual Machines - [Types of Virtual Machines](https://docs.gcore.com/cloud/virtual-instances/types-of-virtual-machines.md): Configure Gcore Virtual Machine types including Standard, GPU, CPU-Optimized, Memory-Optimized, High-frequency, Basic VM, TPM, and Network optimised instances with network bandwidth specifications up to 1 Gbps and traffic policies. - [Create a virtual instance](https://docs.gcore.com/cloud/virtual-instances/create-an-instance.md): Create Linux or Windows Virtual Instances in Gcore Cloud via Customer Portal by configuring image, flavor, volumes, network, and SSH key, or via REST API and Terraform. - [Customize the initial setup for a Virtual Machine](https://docs.gcore.com/cloud/virtual-instances/customize-initial-setup-for-your-instance.md): Configure Virtual Machine initial setup using User Data field with cloud-init YAML syntax to set passwords, create users, configure groups, add SSH keys, install packages, and configure network interfaces via Gcore portal, API, or Terraform. - [Check the operational status of a Virtual Machine](https://docs.gcore.com/cloud/virtual-instances/check-the-operational-status-of-your-instance.md): Retrieve Virtual Machine operational status via the Customer Portal Status column, the Gcore Cloud REST API instances endpoint, or Terraform using the gcore_cloud_instance data source. - [Enable root user on a Linux VM](https://docs.gcore.com/cloud/virtual-instances/enable-root-user-on-a-linux-vm.md): Enable root user permanently on Linux VMs by modifying the cloud-init configuration, or run commands with root privileges temporarily using sudo, sudo su, sudo -i, and sudo -s. ## Connect - [Connect to a Virtual Machine via the Gcore customer portal](https://docs.gcore.com/cloud/virtual-instances/connect/connect-to-your-instance-via-control-panel.md): Connect to Gcore Virtual Machines via VNC console in the Customer Portal using password or SSH key authentication for Windows and Linux VMs. ## Connect via SSH - [Connect to a Virtual Machine via SSH](https://docs.gcore.com/cloud/virtual-instances/connect/connect-via-ssh.md): Connect to Gcore Virtual Machines running Linux via SSH using key pairs or password authentication, with security group configuration and remote session setup. - [Configure and manage SSH keys](https://docs.gcore.com/cloud/virtual-instances/connect/connect-to-your-instance-via-ssh.md): Generate and manage SSH key pairs in Gcore Customer Portal for Virtual Instance authentication, including public key storage, private key download, and key naming with Latin characters, underscores, spaces, and dots (3-63 characters). - [Convert an SSH key to PPK format](https://docs.gcore.com/cloud/ssh-keys/convert-an-ssh-key-from-pem-to-ppk.md): Convert SSH keys to PPK format using PuTTYgen for PuTTY connections to Gcore Virtual Machines, supporting private and public key export. - [Establish SSH connection to a Virtual Instance](https://docs.gcore.com/cloud/virtual-instances/connect/establish-ssh-connection-to-an-instance.md): Establish SSH connection to Virtual Instances using SSH key pairs or password authentication via terminal, WSL, Command Prompt, or PuTTY with floating IP address and firewall rules configured. ## Placement groups - [About placement groups](https://docs.gcore.com/cloud/virtual-instances/placement-groups/about-placement-groups.md): Configure placement groups with Affinity, Anti-affinity, or Soft anti-affinity policies to control Virtual Machine colocation on physical servers for performance optimization or fault tolerance. - [Configure a placement group](https://docs.gcore.com/cloud/virtual-instances/placement-groups/configure-a-placement-group.md): Create and manage Virtual Machine placement groups via the Customer Portal, REST API, or Terraform, covering Affinity, Anti-Affinity, and Soft Anti-Affinity policies, VM assignment during creation, and moving VMs between groups. ## Volumes - [Volumes](https://docs.gcore.com/cloud/virtual-instances/volumes/about-volumes.md): Create boot and regular volumes in Gcore Cloud with High IOPS SSD, Standard, SSD Low-Latency, or deprecated Cold and Ultra types; boot volumes store OS and are required for VM startup, while regular volumes provide general-purpose storage with configurable IOPS limits, bandwidth, and triple data replication. - [Create and configure a volume](https://docs.gcore.com/cloud/virtual-instances/volumes/create-and-configure-volumes.md): Create and configure block storage volumes in Gcore Cloud via Customer Portal, REST API, or Terraform, including creating, attaching, detaching, resizing, and deleting volumes. - [Monitor load and performance of a Virtual Machine](https://docs.gcore.com/cloud/virtual-instances/monitor-load-and-performance-of-your-instance.md): Monitor Virtual Machine performance via the Monitoring tab, covering CPU Utilization, RAM Utilization, Network Traffic, Network Packets, and Disk IOPS. ## Snapshots - [Take a snapshot of your file system](https://docs.gcore.com/cloud/virtual-instances/snapshots/take-a-snapshot-of-your-file-system.md): Create, view, and delete volume snapshots in Gcore Cloud via the Customer Portal or REST API, including Python SDK and Go SDK examples. - [Set up automatic snapshot creation](https://docs.gcore.com/cloud/virtual-instances/snapshots/set-up-automatic-snapshot-creation.md): Create Snapshot Schedules in Gcore Cloud to automate volume snapshot creation on daily, weekly, monthly, yearly, or period intervals with configurable retention and max resource count limits. ## Troubleshooting - [Troubleshoot issues with an SSH connection](https://docs.gcore.com/cloud/virtual-instances/troubleshooting/troubleshoot-issues-with-ssh-connection.md): Troubleshoot SSH connection issues for Gcore VMs - permission denied, SSH key format, firewall rules, floating IP, Windows RDP, and lost key recovery. ## Bare Metal servers - [About Bare Metal](https://docs.gcore.com/cloud/bare-metal-servers/about-bare-metal-servers.md): Deploy dedicated physical Bare Metal servers across multiple global locations with exclusive access to CPU, memory, and networking; configure via Gcore Customer Portal, API, or Terraform with LACP-aggregated network bonds, public and private interfaces, and choice of Ubuntu, CentOS, Debian, Rocky Linux, Windows, or custom ISO images; supports High frequency, Infrastructure, and Storage server types. - [Types of Bare Metal servers](https://docs.gcore.com/cloud/bare-metal-servers/types-of-bare-metal-servers.md): Review Gcore Bare Metal server types, High frequency, Infrastructure, and Storage configurations, CPU specs, RAM, and disk options for gaming, databases, and data-heavy workloads. - [Create a Bare Metal server](https://docs.gcore.com/cloud/bare-metal-servers/create-a-bare-metal-server.md): Create a Bare Metal server on dedicated physical hardware via Customer Portal, REST API, or Terraform. - [Connect to Bare Metal via SSH](https://docs.gcore.com/cloud/bare-metal-servers/connect-to-your-bare-metal-server-via-ssh.md): Connect to Bare Metal servers via SSH using SSH key pairs or password authentication, manage keys in Customer Portal, configure cloud-init user data, and connect with PuTTY or OpenSSH. ## Troubleshooting - [Troubleshoot issues with an SSH connection](https://docs.gcore.com/cloud/bare-metal-servers/troubleshooting/troubleshoot-issues-with-ssh-connection.md): Troubleshoot SSH connection issues to Bare Metal servers including root login permission denied errors, missing console passwords, and lost SSH keys; configure SSH key authentication, add multiple public keys via Customer Portal, and access servers using OS-specific default usernames. ## Advanced DDoS protection - [About advanced DDoS protection for Bare Metal](https://docs.gcore.com/cloud/bare-metal-servers/advanced-ddos-protection/about-advanced-ddos-protection-for-bare-metal-servers.md): Enable Advanced DDoS protection for Bare Metal servers with threat mitigation system (TMS) traffic redirection, ACL configuration, L3/L4/L7 attack filtering, and always-on mode to maintain server uptime without IP blocking during attacks. - [Activate advanced DDoS protection for Bare Metal](https://docs.gcore.com/cloud/bare-metal-servers/advanced-ddos-protection/activate-advanced-ddos-protection-for-bare-metal-servers.md): Enable Advanced DDoS Protection on Bare Metal server network interfaces with public IP addresses by selecting a profile template during server creation or from the Networking tab. ## Images - [About images](https://docs.gcore.com/cloud/images/about-images.md): Create Virtual Machine boot volumes from images containing disk file system structure, data, and pre-installed operating systems or software. - [Upload a custom image](https://docs.gcore.com/cloud/images/upload-an-image-to-the-storage.md): Upload a custom image to Gcore Cloud via the Customer Portal, REST API, or Terraform for use with Virtual Instances, Bare Metal servers, and GPU clusters. - [Manage custom images](https://docs.gcore.com/cloud/images/manage-custom-images.md): View, rename, edit tags, create instances from, and delete custom images in Gcore Cloud via the Customer Portal, REST API, or Terraform. ## Networking - [Create and manage a network](https://docs.gcore.com/cloud/networking/create-and-manage-a-network.md): Create and manage a private network and subnet to connect Virtual Machines within a region, via the Customer Portal, REST API, or Terraform. - [Create and manage a subnetwork](https://docs.gcore.com/cloud/networking/create-and-manage-a-subnetwork.md): Create, update, and delete subnetworks in Gcore Cloud via the Customer Portal, REST API, or Terraform. - [Create and manage a router](https://docs.gcore.com/cloud/networking/create-and-manage-a-router.md): Create and configure a Cloud Router with static routes, SNAT, and subnet interfaces via the Customer Portal, REST API, or Terraform. ## IP address - [Create and configure a floating IP address](https://docs.gcore.com/cloud/networking/ip-address/create-and-configure-a-floating-ip-address.md): Reserve a floating IP address in Gcore Cloud and assign it to a Virtual Machine, Bare Metal server, or Load Balancer using the Customer Portal, REST API, or Terraform. - [Create and configure a reserved IP address](https://docs.gcore.com/cloud/networking/ip-address/create-and-configure-a-reserved-ip-address.md): Reserve a public or private fixed IP address in Gcore Cloud via the Customer Portal, REST API, or Terraform, and use the port ID to assign it to a Virtual Machine, Bare Metal server, or Load Balancer. - [Create and configure a virtual IP address](https://docs.gcore.com/cloud/networking/ip-address/create-and-configure-a-virtual-ip-vip-address.md): Reserve a virtual IP address (VIP) via Customer Portal, REST API, or Terraform, connect VM ports to share the address, enable or disable VIP mode on existing reserved IPs, and configure VRRP-based failover using Keepalived. - [Difference between virtual, floating, and reserved IP addresses](https://docs.gcore.com/cloud/networking/ip-address/difference-between-virtual-floating-and-reserved-ip-addresses.md): Compare Floating IP, Reserved IP, and Virtual IP address types in Gcore Cloud by assignment scope (single VM vs. multiple VMs), failover capability, billing when unassigned, and use cases for external access, high availability, and Bare Metal support. - [Configure an allowed address pair](https://docs.gcore.com/cloud/networking/ip-address/configure-an-allowed-address-pair.md): Assign additional IP addresses to a Virtual Machine's private network interface port via the allowed address pairs API, enabling traffic routing to multiple IPs on a single MAC address with support for up to 10 pairs per port. ## Load balancers - [Create and configure a load balancer](https://docs.gcore.com/cloud/networking/create-and-configure-a-load-balancer.md): Create and configure a Load Balancer with region selection, computing configuration (vCPU, GiB), network type (Public, Private), IP family (IPv4, IPv6, Dual), reserved IP assignment, preferred connectivity method (L2 or L3), listeners, and pools via Customer Portal, REST API, or Terraform. - [Add TLS certificates to a load balancer](https://docs.gcore.com/cloud/networking/load-balancers/add-certificates-to-load-balancer.md): Upload TLS certificates to Gcore Secrets Manager and attach them to TERMINATED HTTPS load balancer listeners to enable SNI-based multi-domain termination; create listeners with a default certificate and add per-domain SNI certificates via the REST API or Terraform. - [Configure mutual TLS authentication](https://docs.gcore.com/cloud/networking/load-balancers/configure-mtls-authentication.md): Configure mutual TLS authentication between Gcore Load Balancers and backend servers using PKCS12 listener certificates, PEM CA certificates, and optional client certificates for mTLS pool configuration via API endpoints. - [Manage load balancers](https://docs.gcore.com/cloud/networking/load-balancers/manage-load-balancers.md): List, inspect, rename, update tags, initiate failover, and delete Load Balancers via the Customer Portal, Gcore REST API with Python SDK, Go SDK, and curl examples, or Terraform. - [Logging for load balancers](https://docs.gcore.com/cloud/networking/load-balancers/logging-for-load-balancers.md): Enable Logging for Load Balancers to collect and store access logs via Gcore Logging service; configure namespace, topic, and retention period; verify guaranteed throughput between Load Balancer regions (Amsterdam, Frankfurt, Tokyo, Istanbul, London, Warsaw, Dubai, Almaty) and Logging destination regions. - [Use annotations for load balancers](https://docs.gcore.com/cloud/networking/load-balancers/use-annotations-for-load-balancers.md): Configure Load Balancer annotations in Gcore Managed Kubernetes to set load balancer type (internal or external), flavor, shared name, floating IP address, fixed IP address, listener connection limits, and pool node selectors via kubectl or service manifest. - [Monitoring for load balancers](https://docs.gcore.com/cloud/networking/load-balancers/monitoring-for-load-balancers.md): Enable Prometheus listener on load balancers to expose metrics endpoint for scraping with Prometheus and Grafana, configurable via Customer Portal with Protocol selection, Port, Connection limit, and security options including CIDR IP ranges, Basic Auth, SSL/TLS certificates, and mTLS authentication. - [Add and configure a firewall](https://docs.gcore.com/cloud/networking/add-and-configure-a-firewall.md): Create and configure security groups and firewall rules for Virtual Machines via Customer Portal, REST API, or Terraform. - [Bring Your Own IP (BYOIP)](https://docs.gcore.com/cloud/networking/byoip.md): Configure Bring Your Own IP (BYOIP) to announce customer-owned public IP address ranges via Gcore ASN or customer ASN (BYOASN) using Letter of Authorization, Route Object (IRR), RPKI ROA, and CIDR prefix registration with Regional Internet Registry. ## File shares - [About file shares](https://docs.gcore.com/cloud/file-shares/about-file-shares.md): Create and manage NFS file shares across Virtual Machines, Bare Metal servers, and Kubernetes pods using the NFS protocol, with support for access rules, snapshots, persistent volumes with RWX mode, and on-demand scaling. - [Configuring file shares](https://docs.gcore.com/cloud/file-shares/configure-file-shares.md): Create NFS-based file shares and mount them to Virtual Machines via Customer Portal, REST API, or Terraform. - [Migrate data from S3 and EFS to Gcore](https://docs.gcore.com/cloud/file-shares/how-to-migrate-data-from-s3.md): Migrate data from Amazon S3 and EFS to Gcore Object Storage and File Shares using rclone CLI tool with AWS IAM credentials, S3 bucket configuration, and NFS mount paths. ## Managed Kubernetes - [About Gcore Managed Kubernetes](https://docs.gcore.com/cloud/kubernetes/about-gcore-kubernetes.md): Deploy Gcore Managed Kubernetes clusters on Virtual Instances or Bare Metal with autoscaling, autohealing nodes, PersistentVolumeClaims storage, Nginx ingress controller networking, and 99.99% SLA backed by Cluster API. - [Bare Metal Kubernetes](https://docs.gcore.com/cloud/kubernetes/bare-metal-kubernetes.md): Deploy Kubernetes worker nodes on Bare Metal servers via Managed Kubernetes to eliminate virtualization layers and gain direct hardware access, improved performance, enhanced security isolation, higher network bandwidth, and lower disk latency. ## Clusters - [Create a Kubernetes cluster](https://docs.gcore.com/cloud/kubernetes/clusters/create-a-kubernetes-cluster.md): Create a Kubernetes cluster by selecting region, version, and configuring node pools with flavor, volume type, volume size, autoscaling limits, and worker node type (Virtual instances, Bare metal instances, or GPU Bare metal instances). Includes REST API, Python SDK, Go SDK, and Terraform examples. - [Upgrade a Kubernetes cluster](https://docs.gcore.com/cloud/kubernetes/clusters/upgrade.md): Upgrade a Kubernetes cluster to a newer version via the Customer Portal, REST API, or Terraform using a rolling update that replaces worker nodes sequentially. ## Connect - [Connect to your nodes via SSH](https://docs.gcore.com/cloud/kubernetes/clusters/connect/connect-to-your-nodes-via-ssh-using-a-floating-ip-address.md): Assign floating IP addresses to Kubernetes cluster nodes and connect via SSH using the floating IP address and private key authentication. - [Install kubectl and connect to a Kubernetes cluster](https://docs.gcore.com/cloud/kubernetes/clusters/connect/install-kubectl-and-connect-to-a-kubernetes-cluster.md): Install kubectl on Windows, Ubuntu, Linux, or macOS and connect to a Gcore Managed Kubernetes cluster using a downloaded kubeconfig file from the Customer Portal. - [Secure Kubernetes cluster with OpenID Connect](https://docs.gcore.com/cloud/kubernetes/clusters/secure-cluster-with-oidc.md): Configure OpenID Connect (OIDC) authentication for Gcore Managed Kubernetes clusters by setting Issuer URL, Client ID, username claim, groups claim, required claims, and signing algorithms to enable centralized SSO access control. ## Autoscaling - [About autoscaling](https://docs.gcore.com/cloud/kubernetes/clusters/autoscaling/about-autoscaling.md): Configure Kubernetes node pool autoscaling limits and disable autoscaling for a pool in the Gcore Customer Portal. - [Change autoscaling limits](https://docs.gcore.com/cloud/kubernetes/clusters/autoscaling/change-autoscaling-limits.md): Configure minimum and maximum node counts for Kubernetes cluster autoscaling pools via the Customer Portal Pools section. - [Create and configure a pool](https://docs.gcore.com/cloud/kubernetes/clusters/autoscaling/create-a-new-pool-in-cluster.md): Create and configure Kubernetes node pool settings, including autoscaling limits, node type, flavor, volume, placement policy, labels, taints, autohealing, and advanced Kubelet and CRI-O options. - [Advanced cluster autoscaler settings](https://docs.gcore.com/cloud/kubernetes/clusters/autoscaling/advanced-cluster-autoscaler-settings.md): Configure Kubernetes cluster autoscaler advanced settings including scan interval, node group expander strategy (random, most-pods, least-waste, price, priority, grpc), max node provision time, pod scale-up delay, unready node thresholds, and scale-down behavior with post-addition and post-deletion delays. - [Configure GPU autoscaling for Kubernetes](https://docs.gcore.com/cloud/kubernetes/clusters/autoscaling/configure-gpu-autoscaling-for-kubernetes.md): Configure Kubernetes Event-Driven Autoscaling (KEDA) to automatically scale GPU resources in Gcore Managed Kubernetes clusters based on GPU utilization, using Bare Metal worker pools with GPU-optimized flavors and minimum/maximum node specifications. - [Add users with limited rights to a Kubernetes cluster](https://docs.gcore.com/cloud/kubernetes/clusters/add-users-with-limited-rights-to-a-kubernetes-cluster.md): Create Kubernetes service accounts with namespace-scoped RBAC permissions and generate kubeconfig files for limited user access via kubectl and Role bindings. - [Monitor load on a specific node](https://docs.gcore.com/cloud/kubernetes/monitor-load-on-a-specific-node.md): Monitor Kubernetes worker node CPU Utilization, RAM Utilization, Network Traffic, and Network Packets metrics via the Monitoring tab in the Gcore Customer Portal, with configurable time range and refresh interval. ## Networking - [About networking in Kubernetes](https://docs.gcore.com/cloud/kubernetes/networking/about-networking-in-kubernetes.md): Configure Kubernetes Services, Ingress objects, and Ingress Controllers to route internal and external traffic to pods using single IP addresses, path-based rules, and load balancing across pod replicas. - [Install nginx Ingress controller](https://docs.gcore.com/cloud/kubernetes/networking/install-and-set-up-the-nginx-ingress-controller.md): Deploy nginx Ingress Controller on Gcore Managed Kubernetes using Helm, which automatically provisions a Load Balancer resource for routing external traffic to cluster services via Ingress manifests. - [Use Nginx Ingress Controller](https://docs.gcore.com/cloud/kubernetes/networking/use-the-nginx-ingress-controller.md): Create Ingress objects with Nginx ingressClassResource, specifying Service name, port, URL path, and apply via kubectl to route traffic through Nginx Ingress Controller. ## Storage - [Create a PVC and bind to a pod](https://docs.gcore.com/cloud/kubernetes/storage/create-a-pvc-and-bind-it-to-a-pod.md): Create PersistentVolumeClaim (PVC) resources in Gcore Managed Kubernetes by defining StorageClass with disk types (standard, ssd_highiops, ssd_lowlatency), then binding PVC to pods using kubectl with accessModes, storage capacity, and volumeBindingMode parameters. - [Configure NFS storage for Managed Kubernetes](https://docs.gcore.com/cloud/kubernetes/storage/configure-nfs-csi-driver-for-kubernetes.md): Configure NFS CSI driver to dynamically provision and attach Gcore File Shares as persistent volumes in Managed Kubernetes clusters using StorageClass, PersistentVolumeClaim, and NFS protocol within the same project and network. - [Troubleshooting a node in a "Not Ready" state](https://docs.gcore.com/cloud/kubernetes/troubleshooting-not-ready-state.md): Diagnose Kubernetes nodes in Not Ready state by listing nodes with kubectl, checking node conditions (MemoryPressure, DiskPressure, Ready), reviewing Capacity and Allocatable resources, and examining Kubelet logs for certificate, authentication, and network errors. ## Managed PostgreSQL - [About managed PostgreSQL](https://docs.gcore.com/cloud/managed-database-postgresql.md): Deploy Gcore Managed PostgreSQL servers with configurable flavor, vCPU/RAM, storage capacity, connection pooler mode, and volume type; supports PostgreSQL 13, 14, and 15 with high availability via synchronous replication, IP access control lists, and multi-region data center placement. - [Manage a PostgreSQL server](https://docs.gcore.com/cloud/managed-database-postgresql/manage-postgresql-servers.md): Create a managed PostgreSQL cluster in Gcore Cloud via Customer Portal or REST API. - [Backup and restore PostgreSQL database for Managed PostgreSQL using external utilities](https://docs.gcore.com/cloud/managed-database-postgresql/backup-and-restore-postgresql-database-for-gcore-managed-database-for-postgresql-using-external-utilities.md): Backup and restore Managed PostgreSQL databases using pg_dump and pg_restore utilities with SQL, TAR, custom, and directory formats; retrieve connection credentials (hostname, username, password, port) from Customer Portal. ## Secrets manager - [Configure secrets for HTTPS load balancer](https://docs.gcore.com/cloud/secrets-manager/upload-a-pkcs12-file.md): Create SSL/TLS secrets in Gcore Secrets Manager by uploading PKCS12 files or manually entering certificate, certificate chain, and private key for HTTPS Load Balancer listeners via Customer Portal, REST API, or Terraform. ## Function as a service - [About Function as a Service](https://docs.gcore.com/cloud/faas/about-function-as-a-service.md): Deploy serverless functions via Gcore FaaS using HTTP endpoints, Kubernetes pods, zero-scaler for automatic scaling from 0 pods with configurable timeout periods, and auto-scaler for maintaining minimum pod replicas with CPU and memory allocation. - [Authenticate to functions with API keys](https://docs.gcore.com/cloud/faas/authenticate-to-functions-with-api-keys.md): Create and manage API keys for Gcore Functions to authenticate endpoint access, configure expiration dates, specify authorized functions, and handle key rotation via the Cloud portal. - [Code examples for supported FaaS runtimes](https://docs.gcore.com/cloud/faas/code-examples-for-supported-faas-runtimes.md): Create FaaS functions in .NET, Go, Java, Node.js, and Python runtimes with code examples for basic handlers, dependency management via .csproj/go.mod/pom.xml/package.json/requirements.txt, and request/response object access through event parameters. ## Container as a service - [About container as a service](https://docs.gcore.com/cloud/caas.md): Deploy containerized applications in Gcore Container as a Service across supported regions using container images, managed via customer portal or REST API without Kubernetes or VM infrastructure management. - [Create a container](https://docs.gcore.com/cloud/caas/create-a-container.md): Deploy containerized applications in Gcore Container as a Service via Customer Portal or REST API. - [Build and deploy containers to CaaS via GitHub Actions](https://docs.gcore.com/cloud/caas/build-and-deploy-containers-to-caas-via-github-actions.md): Deploy containers to Gcore Container as a Service via GitHub Actions workflow using the deploy-container action with required fields - API token, project ID, region ID, container name, image name, and optional parameters for port, description, environment variables, flavor, scale-down duration, minimum/maximum instances. - [Manage containers](https://docs.gcore.com/cloud/caas/manage-containers.md): Get status, update configuration, stop, start, retrieve logs, and delete CaaS containers via the Customer Portal or REST API using GET, PATCH, and DELETE requests on the /cloud/v1/caas/{project_id}/{region_id}/containers endpoint. ## Container registry - [Container registry](https://docs.gcore.com/cloud/container-registry.md): Create and manage OCI-compatible Docker image registries with per-user push and pull permissions, accessible via Docker CLI, API, and Gcore Customer Portal for use with Everywhere Inference, Container as a Service, and Managed Kubernetes. - [Create a Container Registry](https://docs.gcore.com/cloud/container-registry/create-container-registry.md): Create a Container Registry, add registry users with configurable permissions and credential expiration, and push or pull OCI-compatible images via the Customer Portal or REST API using Python and Go SDK. - [Manage container registries](https://docs.gcore.com/cloud/container-registry/manage-container-registries.md): Manage Container Registry storage limits, repositories, artifacts, tags, and users via the Customer Portal or REST API using Python and Go SDK. ## Managed logging - [About managed logging](https://docs.gcore.com/cloud/logging-as-a-service/about-logging-as-a-service.md): Configure Managed Logging to collect logs from Virtual Machines and Bare Metal servers using Kafka-compatible log shippers like Fluent Bit, Filebeat, or Logstash, then access and analyze logs via OpenSearch Dashboards with support for text/JSON format, up to 225 JSON fields, and 1 MB maximum message size. - [Configure logging and view logs](https://docs.gcore.com/cloud/logging-as-a-service/configure-logging-and-view-your-logs.md): Configure Gcore Managed Logging by selecting a region, creating a human-readable namespace (2-32 lowercase alphanumeric characters), creating Kafka topics, generating credentials, and connecting log shippers (Fluent Bit, Filebeat, Logstash) with Kafka endpoints to export logs to OpenSearch Dashboards with @timestamp indexing. ## Install a log shipper - [Install and configure Filebeat](https://docs.gcore.com/cloud/logging-as-a-service/install-a-log-shipper/install-and-configure-filebeat.md): Configure Filebeat log shipping with input sources (file paths, TCP, UDP, syslog) and output.kafka destination parameters (hosts, topic, sasl.mechanism, sasl.username, password, ssl.enabled) to forward logs to Gcore Managed Logging via Kafka endpoint. - [Install and configure Fluent Bit](https://docs.gcore.com/cloud/logging-as-a-service/install-a-log-shipper/install-and-configure-fluent-bit.md): Configure Fluent Bit input and output sections with tail data source, Kafka brokers endpoint, topic name, and SASL authentication parameters (rdkafka.security.protocol, rdkafka.sasl.mechanism, rdkafka.sasl.username, rdkafka.sasl.password) to ship logs to Gcore Managed Logging via OpenSearch Dashboards. - [Install and configure Fluentd](https://docs.gcore.com/cloud/logging-as-a-service/install-a-log-shipper/install-and-configure-fluentd.md): Configure Fluentd with Kafka Integration Plugin to stream logs to Gcore Managed Logging using brokers, username, password, default_topic, scram_mechanism, sasl_over_ssl, and fluent-plugin-kafka output plugin. - [Install and configure Logstash](https://docs.gcore.com/cloud/logging-as-a-service/install-a-log-shipper/install-and-configure-logstash.md): Configure Logstash with Kafka output plugin to send logs to Gcore Managed Logging using topic_id, bootstrap_servers, sasl.mechanism, security_protocol, sasl_jaas_config, key_serializer, and value_serializer parameters. - [Prometheus exporter](https://docs.gcore.com/cloud/logging-as-a-service/prometheus-exporter.md): Configure Prometheus targets to scrape OpenSearch index metrics from Managed Logging via HTTPS Basic Authentication using the Prometheus exporter endpoint, exposing gauge metrics for document indexing, query cache, search scrolls, segment memory, and shard statistics. - [View Gcore Managed Logging data in Grafana with OpenSearch plugin](https://docs.gcore.com/cloud/logging-as-a-service/view-opensearch-logs-in-Grafana.md): Configure Gcore Managed Logging integration with Grafana using the OpenSearch Grafana Data Source plugin, setting HTTP parameters (URL, Access, Allowed cookies, Timeout) and Basic authentication credentials to display logs from OpenSearch Dashboards. ## Terraform - [Manage Cloud resources via Terraform v0](https://docs.gcore.com/cloud/manage-cloud-via-terraform.md): Create and manage Gcore Cloud resources — Virtual Machines, Bare Metal servers, Kubernetes clusters, Load Balancers, and networks — using Terraform provider v0. - [Manage Cloud resources via Terraform v2](https://docs.gcore.com/cloud/manage-cloud-via-terraform-v2.md): Create and manage Gcore Cloud resources — Virtual Machines, Bare Metal servers, Kubernetes clusters, Load Balancers, networks, volumes, security groups, and IP addresses — using Terraform provider v2. - [Manage cloud resources via Ansible](https://docs.gcore.com/cloud/manage-cloud-via-ansible.md): Configure Gcore Cloud resources using Ansible Galaxy Collection modules and plugins for provisioning, deploying, and orchestrating instances, volumes, networks, and other cloud services via playbooks with API key authentication and region/project parameters. ## Use cases - [Set up a mailing server in a Gcore Cloud VM](https://docs.gcore.com/cloud/use-cases/set-up-a-mailing-server-in-gcore-cloud-vm.md): Configure Postfix and Dovecot mail server components on Gcore Cloud VM with SMTP port 25 access, SSL/TLS parameters, mailbox creation, and DNS records for email delivery on Ubuntu and Debian.