Actions190
- Auth Actions
- Backup Actions
- Custom Templates Actions
- Docker Actions
- Edge Groups Actions
- Edge Jobs Actions
- Edge Stacks Actions
- Endpoint Groups Actions
- Endpoints Actions
- Endpoint Delete Batch
- Endpoint List
- Endpoint Create
- Endpoint Delete
- Endpoint Inspect
- Endpoint Update
- Endpoint Association Delete
- Endpoint Dockerhub Status
- Endpoint Edge Status Inspect
- Endpoint Force Update Service
- Endpoint Registries List
- Endpoint Registry Access
- Endpoint Settings Update
- Endpoint Snapshot
- Endpoint Update Relations
- Gitops Actions
- Helm Actions
- Intel Actions
- Kubernetes Actions
- Get All Kubernetes Applications
- Get All Kubernetes Applications Count
- Delete Cluster Role Bindings
- Delete Cluster Roles
- Get All Kubernetes Cluster Role Bindings
- Get All Kubernetes Cluster Roles
- Get All Kubernetes Config Maps
- Get All Kubernetes Config Maps Count
- Get Kubernetes Cron Jobs
- Delete Cron Jobs
- Get Kubernetes Dashboard
- Get All Kubernetes Ingress Controllers
- Update Kubernetes Ingress Controllers
- Get All Kubernetes Cluster Ingresses
- Get All Kubernetes Cluster Ingresses Count
- Delete Kubernetes Ingresses
- Get Kubernetes Jobs
- Delete Jobs
- Get Kubernetes Max Resource Limits
- Get Applications Resources
- Get Kubernetes Metrics For All Nodes
- Get Kubernetes Metrics For Node
- Get Kubernetes Metrics For All Pods
- Get Kubernetes Metrics For Pod
- Delete Kubernetes Namespace
- Get Kubernetes Namespaces
- Create Kubernetes Namespace
- Update Kubernetes Namespace Deprecated
- Get Kubernetes Namespace
- Update Kubernetes Namespace
- Get Kubernetes Config Map
- Get Kubernetes Ingress Controllers By Namespace
- Update Kubernetes Ingress Controllers By Namespace
- Get All Kubernetes Ingresses
- Create Kubernetes Ingress
- Update Kubernetes Ingress
- Get Kubernetes Ingress
- Get Kubernetes Secret
- Get Kubernetes Services By Namespace
- Create Kubernetes Service
- Update Kubernetes Service
- Kubernetes Namespaces Toggle System
- Get Kubernetes Volumes In Namespace
- Get Kubernetes Namespaces Count
- Get Kubernetes Nodes Limits
- Get Kubernetes RBAC Status
- Delete Role Bindings
- Get Kubernetes Role Bindings
- Get Kubernetes Roles
- Delete Roles
- Get Kubernetes Secrets
- Get Kubernetes Secrets Count
- Delete Service Accounts
- Get Kubernetes Service Accounts
- Get Kubernetes Services
- Get All Kubernetes Services Count
- Delete Kubernetes Services
- Get All Kubernetes Volumes
- Get Kubernetes Volume
- Get All Kubernetes Volumes Count
- Get Kubernetes Config
- Ldap Actions
- Registries Actions
- Resource Controls Actions
- Settings Actions
- Ssl Actions
- Stacks Actions
- Stack List
- Stack Delete
- Stack Inspect
- Stack Update
- Stack Associate
- Stack File Inspect
- Stack Update Git
- Stack Git Redeploy
- Stack Migrate
- Stack Start
- Stack Stop
- Stack Create Kubernetes Git
- Stack Create Kubernetes File
- Stack Create Kubernetes Url
- Stack Create Docker Standalone File
- Stack Create Docker Standalone Repository
- Stack Create Docker Standalone String
- Stack Create Docker Swarm File
- Stack Create Docker Swarm Repository
- Stack Create Docker Swarm String
- Stack Delete Kubernetes By Name
- Webhook Invoke
- Tags Actions
- Team Memberships Actions
- Teams Actions
- Templates Actions
- Upload Actions
- Users Actions
Kubernetes → Create Kubernetes Service
AI-generatedOverview
This node operation allows users to create a Kubernetes Service within a specified Kubernetes cluster environment. It is useful for automating the deployment and management of services in Kubernetes, enabling seamless integration with Kubernetes APIs directly from n8n workflows. Typical use cases include setting up new services for applications, exposing pods internally or externally, and managing service lifecycles programmatically.
For example, you might use this node to create a LoadBalancer service that exposes your application to external traffic or a ClusterIP service for internal communication between pods.
Properties
| Name | Meaning |
|---|---|
| Id | Environment identifier: a numeric ID representing the target Kubernetes environment. |
| Namespace | Namespace name: the Kubernetes namespace where the service will be created. |
| Body | Service definition: a JSON string defining the Kubernetes Service resource specification. |
- The Body property expects a full Kubernetes Service manifest in JSON format, specifying metadata, spec, ports, selectors, and other relevant fields according to Kubernetes API conventions.
Output
The node outputs the response from the Kubernetes API after attempting to create the service. This output is provided in the json field and typically contains the details of the created Service resource, including its metadata, status, and spec as returned by the Kubernetes API server.
If the creation is successful, the output JSON reflects the newly created service object. If there is an error (e.g., invalid body, namespace not found), the output will contain error information accordingly.
No binary data output is involved in this operation.
Dependencies
- Requires access to a Kubernetes cluster API endpoint.
- Needs an API key or token credential configured in n8n to authenticate requests against the Kubernetes API.
- The node uses HTTP requests to interact with the Kubernetes REST API; thus, network connectivity and proper permissions are necessary.
Troubleshooting
- Invalid Service Definition: If the JSON in the Body property is malformed or does not conform to Kubernetes Service schema, the API will reject the request. Validate the JSON structure before sending.
- Namespace Not Found: Specifying a non-existent namespace will cause the API to return an error. Ensure the namespace exists in the cluster.
- Authentication Errors: Missing or incorrect API credentials will result in authorization failures. Verify that the API token or key has sufficient permissions.
- Network Issues: Connectivity problems to the Kubernetes API endpoint can cause timeouts or connection errors. Check network settings and endpoint accessibility.
Common error messages usually come directly from the Kubernetes API and should be interpreted based on standard Kubernetes API error codes and messages.